Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > >> Let's take it out and wait to see if anyone really still wants it. > > > Just when I am ready to throw it away, I come up with a use for the > > function: > > > test=> select * from pg_stat_activity where procpid != backend_pid(); > > > This shows all activity _except_ my session, which pgmonitor or others > > may want to use, and I can think of no other way to do it. > > Hm. Actually this seems like an argument for exposing MyBackendId, since > what pg_stat_activity really depends on is BackendId. But as that view > is presently defined, you'd not be able to write > WHERE backendid = my_backend_id() > because the view doesn't expose backendid.
Yes. > > Comments? Maybe this is why it should be called pg_backend_id and put > > in the stat section. > > *Please* don't call it pg_backend_id --- that invites confusion with > BackendId which is a different thing. > > I'd suggest pg_backend_pid. Sorry, I mean pg_backend_pid. I could expose backend_id but it may confuse people so pid is probably better. If you had the id, you could use pg_stat_get_backend_pid() to get the pid. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
