| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Greg Stark <gsstark(at)mit(dot)edu>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Chander Ganesan <chander(at)otg-nc(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: We should Axe /contrib/start-scripts |
| Date: | 2009-08-27 00:59:02 |
| Message-ID: | 4A95DA56.9090100@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
>
> I was actually having second thoughts about the idea of using file
> locking. The only environment in which I've heard of file locks not
> being trustworthy is NFS, and if you're running a DB on NFS you've
> probably got worse problems than this one. Notably, if you mistakenly
> try to start postmasters on two different machines against the same
> NFS-mounted directory, the PID-based interlock will certainly fail, while
> file locking might save you. So maybe we should take another look at
> that. Has anyone heard of other contexts in which file locks don't
> work? Has Windows got them?
>
>
>
Yes. But they are mandatory rather than advisory, I believe.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-08-27 01:02:40 | Re: We should Axe /contrib/start-scripts |
| Previous Message | Tom Lane | 2009-08-27 00:38:49 | Re: We should Axe /contrib/start-scripts |