Re: procpid?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

> For me, the litmus test is whether the change provides enough
> improvement that it outweighs the disruption when the user runs into
> it.

For the procpid that started all of this, the clear answer is no. I'm
surprised people seriously considered making this change. It's a
historical accident: document and move on. And if we are going to
talk about changing misnamed things, I've got a whole bunch of others
I could throw at you (such as abbreviation rules: blks_read on the
one extreme, and autovacuum_analyze_scale_factor on the other) :)

> This is why I suggested a specific, useful, and commonly requested
> (to me at least) change to pg_stat_activity go along with this.

+1. The procpid change is silly, but fixing the current_query field
would be very useful. You don't know how many times my fingers
have typed "WHERE current_query <> '<IDLE>'"

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

iEYEAREDAAYFAk34IRoACgkQvJuQZxSWSsi0dgCgi37mrLYbD6G3dS99GPbSFhHW
EjYAniZNpRUXxYmhBHfb1k1LsMSoOHE7
=61nA
-----END PGP SIGNATURE-----