| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Addition of authenticated ID to pg_stat_activity |
| Date: | 2021-04-27 01:54:02 |
| Message-ID: | YIduuttfFeQ1WvR+@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 27, 2021 at 09:26:11AM +0800, Julien Rouhaud wrote:
> -1. It's already annoying enough to have to type "WHERE pid !=
> pg_backend_pid()" to exclude my own backend, and I usually need it quite often.
> Unless we add some new view which integrate that, something like
> pg_stat_activity_except_me with a better name. I also don't see how we could
> join a new dedicated view with the old one without that information.
Err, sorry for the confusion. What I meant here is to also keep the
PID in pg_stat_activity, but also add it to this new view to be able
to join things across the board.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | houzj.fnst@fujitsu.com | 2021-04-27 02:09:01 | RE: Parallel INSERT SELECT take 2 |
| Previous Message | Masahiko Sawada | 2021-04-27 01:47:08 | Re: Performance degradation of REFRESH MATERIALIZED VIEW |