Re: Multiple backends on a single physical database

I have just done this. There are three things I have found necessary:
1. Only one backend can use the postmaster.pid file. You must edit the
sourcecode for the other backends before you compile it.
2. If you have backends A,B,C and A makes a modification to the data, B and
C need to be restarted before they can see the changes.
3. Startup scripts for backends B and C that do not use the postmaster.pid
file need to be changed, specifically the method of stopping them. I do a
`ps` and awk out the pid to kill it. This is necessary to prevent removing
the lockfile from backend A.

I plan to use a high speed network storage device to accomplish this setup
effectively.

----- Original Message -----
From: "Anuradha Ratnaweera" <anuradha(at)gnu(dot)org>
To: <pgsql-admin(at)postgresql(dot)org>
Sent: Wednesday, October 09, 2002 11:09 PM
Subject: [ADMIN] Multiple backends on a single physical database

>
> I am wondering if it is sane to mount PGDATA over NFS on many
> machines and run posmaster backends on them, so that all the
> postmasters are using the same database.
>
> Obviously performance is going to suffer because network traffic
> is going to be high, but later we may use a distributed filesystem
> with replications instead of NFS.
>
> Thanks in advance.
>
> Anuradha
>
> --
>
> Debian GNU/Linux (kernel 2.4.18-xfs-1.1)
>
> There is more simplicity in the man who eats caviar on impulse than in the
> man who eats Grape-Nuts on principle.
> -- G.K. Chesterton
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>