-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
- --On Thursday, January 17, 2008 01:12:54 -0500 Tom Lane <[EMAIL PROTECTED]> wrote: > "Marc G. Fournier" <[EMAIL PROTECTED]> writes: >> [EMAIL PROTECTED] (Mischa Sandberg) writes: >>> Unfortunately, with multiple jails running PG servers and (due to app >>> limitations) all servers having same PGPORT, you get the situation that >>> when jail#2 (,jail#3,...) server comes up, it: >>> - detects that there is a shm seg with ipc key 5432001 >>> - checks whether the associated postmaster process exists (with kill -0) >>> - overwrites the segment created and being used by jail #1 > >> Easiest fix: change the UID of the user running the postmaster (ie. pgsql) so >> that each runs as a distinct UID (instead of distinct PGPORT) ... been doing >> this since moving to FreeBSD 6.x ... no patches required ... > > Sure, but in the spirit of "belt and suspenders too", I'd think that > doing that *and* something like Mischa's proposal wouldn't be bad. No arguments here, just pointing out that changing PGPORT isn't/wasnt' the only way of addressing this problem ... if we can do something more 'internal', it would definitely make life alot easier ... - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHjvMR4QvfyHIvDvMRAjJuAKCAYGkyvDOMkA6wqeQ7nAqoA1mkRQCdG+5n aD1uG+zUtevdJGJ3BsqeDAs= =Y0DY -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
