On Wed, 11 May 2005, Marton Kenyeres wrote:
Dag-Erling Smørgrav wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
'k, I've been doing multiple since 7.2 on the same machine, all on the
same port, all different IPs, all on 4.x servers ... have never had an
issue with crashes (its pretty much my
Dag-Erling Smørgrav wrote:
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
'k, I've been doing multiple since 7.2 on the same machine, all on the
same port, all different IPs, all on 4.x servers ... have never had an
issue with crashes (its pretty much my most stable 4.x server) ...
It was never po
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> 'k, I've been doing multiple since 7.2 on the same machine, all on the
> same port, all different IPs, all on 4.x servers ... have never had an
> issue with crashes (its pretty much my most stable 4.x server) ...
It was never possible. 8.0 has a ha
On Tue, 3 May 2005, [iso-8859-1] Dag-Erling Smørgrav wrote:
PostgreSQL has always had this problem, both on 4.x and 5.x. A hack was
put in place last November to work around it, but it still exists, and
while it may now be possible (with 8.0) for multiple postmasters to run
on the same machine
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> You've all lost me here ... what exactly is the problem?
You can't run multiple instances of PostgreSQL on the same machine
(even in chroot or jail, even without TCP/IP support) without changing
the port number in postgresql.conf. PostgreSQL create
Richard Coleman <[EMAIL PROTECTED]> writes:
> 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 identifi
On 5/2/2005 4:03 PM, Marc G. Fournier wrote:
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 susp
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,
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 we
An unknown poster wrote:
> AFAIR PostgreSQL generates the shared memory identifier based on
> the port it is runing on. It is possible to run two instances of
> PostgreSQL on different ports, so it should work if they are in
> seperate jails.
Correct.
Alexander Rusinov <[EMAIL PROTECTED]> writes:
Just add the following line to your /etc/rc.conf
jail_sysvipc_allow="YES"
and ipc configuration will be shared with the jails
I have IPC enabled for jails already. So unfortunately this is not a
solution.
Is anybody here who do run several jailed PostgreSQL servers?
AFAIR PostgreSQL generates
Marc G. Fournier wrote:
On Tue, 26 Apr 2005, Bill Moran wrote:
Alexander Rusinov <[EMAIL PROTECTED]> wrote:
Hi,
I need to run a number of PostgreSQL servers in different FreeBSD
jails.
I managed to run a first instance of PostgreSQL server in a jail, but
after I launch a new server in another jail
"Marc G. Fournier" <[EMAIL PROTECTED]> wrote:
> On Tue, 26 Apr 2005, Bill Moran wrote:
>
> > Alexander Rusinov <[EMAIL PROTECTED]> wrote:
> >> Hi,
> >>
> >> I need to run a number of PostgreSQL servers in different FreeBSD jails.
> >> I managed to run a first instance of PostgreSQL server in a ja
On Tue, 26 Apr 2005, Bill Moran wrote:
Alexander Rusinov <[EMAIL PROTECTED]> wrote:
Hi,
I need to run a number of PostgreSQL servers in different FreeBSD jails.
I managed to run a first instance of PostgreSQL server in a jail, but
after I launch a new server in another jail the first one starts to
Renato Botelho wrote:
On 26/04/05, Alexander Rusinov <[EMAIL PROTECTED]> wrote:
Hi,
I need to run a number of PostgreSQL servers in different FreeBSD jails.
I managed to run a first instance of PostgreSQL server in a jail, but
after I launch a new server in another jail the first one starts to
r
Spartak Radchenko wrote:
On Tue, Apr 26, 2005 at 05:58:27PM +0300, Alexander Rusinov wrote:
Hi,
I need to run a number of PostgreSQL servers in different FreeBSD jails.
Is SYSV IPC allowed for jails? It's not enabled by default.
Yes, it is on:
security.jail.sysvipc_allowed: 1
I wouln't b
On 26/04/05, Alexander Rusinov <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I need to run a number of PostgreSQL servers in different FreeBSD jails.
> I managed to run a first instance of PostgreSQL server in a jail, but
> after I launch a new server in another jail the first one starts to
> return an err
Alexander Rusinov <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I need to run a number of PostgreSQL servers in different FreeBSD jails.
> I managed to run a first instance of PostgreSQL server in a jail, but
> after I launch a new server in another jail the first one starts to
> return an error message
On Tue, Apr 26, 2005 at 05:58:27PM +0300, Alexander Rusinov wrote:
> Hi,
>
> I need to run a number of PostgreSQL servers in different FreeBSD jails.
Is SYSV IPC allowed for jails? It's not enabled by default.
--
Spartak Radchenko SVR1-RIPE
___
freebs
Hi,
I need to run a number of PostgreSQL servers in different FreeBSD jails.
I managed to run a first instance of PostgreSQL server in a jail, but
after I launch a new server in another jail the first one starts to
return an error messages like the following:
semctl(1507328, 4, SETVAL, 0) faile
20 matches
Mail list logo
