| From: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Oliver Elphick <olly(at)lfix(dot)co(dot)uk> |
| Cc: | Vince Vielhaber <vev(at)michvhf(dot)com>, "J(dot) M(dot) Brenner" <doom(at)kzsu(dot)stanford(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: location of the configuration files |
| Date: | 2003-02-14 02:59:25 |
| Message-ID: | 200302132159.25130.lamar.owen@wgcr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thursday 13 February 2003 21:49, Tom Lane wrote:
> Oliver Elphick <olly(at)lfix(dot)co(dot)uk> writes:
> > need is verified, I could do this by moving the pid file from
> > $PGDATA/postmaster.pid to /var/run/postgresql/5432.pid and similarly for
> > other ports. This would also have the benefit of being more FHS
> > compliant What do people think about that?
> No chance at all. Breaking the connection between the data directory
> and the postmaster.pid file means we don't have an interlock against
> starting two postmasters in the same data directory.
It's not a pid file in the /var/run sense, really. It's an interlock for
PGDATA. So it might be argued that postmaster.pid is misnamed.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2003-02-14 03:04:20 | Re: [HACKERS] More benchmarking of wal_buffers |
| Previous Message | Tom Lane | 2003-02-14 02:49:16 | Re: location of the configuration files |