| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | mgr inż(dot) Jacek Bzdak <jbzdak(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Fwd: Problems with pg_stat_activity view |
| Date: | 2013-11-03 02:50:36 |
| Message-ID: | 22710.1383447036@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
=?ISO-8859-2?Q?mgr_in=BF=2E_Jacek_Bzdak?= <jbzdak(at)gmail(dot)com> writes:
> Maybe just fix pg_stat_activity so it uses LEFT JOIN, to cover such case. I
> guess it shouldnt break any code?
Meh ... that would result in the usename column being possibly NULL,
which I bet applications aren't expecting either. I'm not necessarily
against this, but I'm not sure it'll make things much better.
Anybody else have an opinion?
(Of course, the real fix would be to prevent dropping user IDs that
correspond to any live session, but that's not terribly easy either,
especially if you think about transient settings such as SET ROLE.
Overall I'm not convinced this is a case worth spending a lot of
effort on.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mgr inż. Jacek Bzdak | 2013-11-03 20:05:21 | Re: Fwd: Problems with pg_stat_activity view |
| Previous Message | Peter Hicks | 2013-11-03 00:49:45 | Re: BUG #8576: 'btree index keys must be ordered by attribute' |