Date: Mon, 2 May 2005 18:03:31 -0300 (ADT) From: "Marc G. Fournier" <scrappy@hub.org> To: Richard Coleman <rcoleman@criticalmagic.com> Cc: Alexander Rusinov <boot@eurocom.od.ua> Subject: Re: PostgreSQL in FreeBSD jails Message-ID: <20050502180152.I53065@ganymede.hub.org> In-Reply-To: <4276910A.3040100@criticalmagic.com> References: <426E5713.3010906@eurocom.od.ua> <747dc8f30504260812ee3c47e@mail.gmail.com> <426E5EA5.8000703@eurocom.od.ua> <426F3AFA.9020900@konvergencia.hu> <426F5A6E.4050208@eurocom.od.ua> <86acndmyky.fsf@xps.des.no> <4276910A.3040100@criticalmagic.com>
next in thread | previous in thread | raw e-mail | index | archive | help
yOn Mon, 2 May 2005, Richard Coleman wrote: > Dag-Erling Smørgrav wrote: >> There are two possible solutions: >> >> - hack the SysV IPC code to use separate namespaces for each jail >> >> - make PostgreSQL use POSIX shared memory instead of SysV shared >> memory >> >> I suspect that the latter is significantly easier, and would probably >> improve performance as well. >> >> DES > > It might be easier to hack PostgreSQL so that the shared memory identifier > depends not only on the port, but also on the IP address (which will of > course be different for each jail). Or better yet, to be able to specify the > shared memory identifier to use directly in the config file. You've all lost me here ... what exactly is the problem? PostgreSQL works under FreeBSD 4.x jails without any modifications, so how is PostgreSQL itself currently broken? It seems to me that the problem is with FreeBSD 5.x's jail side of things, if the same daemon runs fine under 4.x, but, nto under 5.x ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050502180152.I53065>