Re: procpid? - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: procpid?
Date
Msg-id 4a8c958d46b422c858499d61c8800fb0@biglumber.com
Whole thread Raw
In response to Re: procpid?  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: procpid?
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


> At any rate, I like "sessions".  That's what it is, after all.  But I
> will note that we had better be darn sure to make all the changes we
> want to make in one go, because I dowanna have to create pg_sessions2
> (or pg_tessions?) in a year or three.

Or perhaps pg_connections. Yes, +1 to making things fully backwards 
compatible by keeping pg_stat_activity around but making a better 
designed and better named table (view/SRF/whatever).

Sounds like perhaps a wiki page to start documenting some of our 
monitoring shortcomings? Might as well fix as much as we can in one 
swoop.


- -- 
Greg Sabino Mullane greg@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201106151246
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAk344ioACgkQvJuQZxSWSshy9wCgnrj4lQkaomsgS55yq9KI0HBl
P2UAoI62Tkt9/U62l0Bxv/KfQUUlL/NF
=aaTL
-----END PGP SIGNATURE-----




pgsql-hackers by date:

Previous
From: PostgreSQL - Hans-Jürgen Schönig
Date:
Subject: Re: bad posix_fadvise support causes initdb to exit ungracefully
Next
From: Robert Haas
Date:
Subject: Re: pg_upgrade using appname to lock out other users