On Fri, Jan 8, 2010 at 10:07, Stephen Frost <sfr...@snowman.net> wrote: > * Tom Lane (t...@sss.pgh.pa.us) wrote: >> I don't want to go to the trouble of creating (and documenting) a >> configure option for this. Much less a GUC ;-) > > Requiring a custom build to disable it would be horrible, in my view. > Or, at best, just means that the packagers won't enable it, which > obviously would be less than ideal.
FWIW I agree. > Sorry if it's a pain, but I think it needs to either be configurable or > not done. As I said before, it definitely needs to handle failure > gracefully, but I worry that even that won't be sufficient in some > cases. Just thinking about how we run PG under VServers and Linux > Containers and whatnot, we ran into some issues with OpenSSH trying to > monkey with proc values and I'd really hate to run into the same issues > with PG. As long as the VM/container you are running under wont kill postmaster for trying to access proc-- the patch I posted should work fine. It just ignores any error (I assumed you might be running in a chroot without proc or some such). -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
