From: Achilleas Mantzios <achill@matrix.gatewaynet.com>
To: pgsql-admin@postgresql.org
Subject: Re: postgresql in FreeBSD jails: proposal
Date: Thu, 17 Jan 2008 10:21:33 +0200
Message-ID: <200801171021.33707.achill@matrix.gatewaynet.com> (raw)
In-Reply-To: <fmmqfh$buq$3@news.hub.org>
References: <1200501702.478e33c61b74e@webmail.telus.net>
<fmmqfh$buq$3@news.hub.org>
Στις Thursday 17 January 2008 07:52:50 ο/η Marc G. Fournier έγραψε:
> mischa_sandberg@telus.net (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 ...
Hi Marc,
what happened with the patches at http://docs.freevps.com/doku.php?id=freebsd:changelog?
Those patches are supposed to make IPC run without collisions in many jails, thus solving the
classic problem with postgresql, allowing the admin to use the same uid, PGPORT in all pgsql
server instances.
Do you know if any of this stuff make it anywhere in official FreeBSD?
--
Achilleas Mantzios
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: achill@matrix.gatewaynet.com
Subject: Re: postgresql in FreeBSD jails: proposal
In-Reply-To: <200801171021.33707.achill@matrix.gatewaynet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox