| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | korry <korry(at)appx(dot)com>, Andreas Joseph Krogh <andreak(at)officenet(dot)no>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: file-locking and postmaster.pid |
| Date: | 2006-05-24 21:33:06 |
| Message-ID: | 20060524213306.GB7412@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan wrote:
> Alvaro Herrera wrote:
> >Alvaro Herrera wrote:
> >
> >>Note that it may fail! This seems to indicate that some platforms do
> >>not provide either locking mechanism.
> >
> >(Which means the whole discussion is a waste of time)
>
> Umm, no, I don't think so. It will block instead of failing unless you
> request a non blocking call. Failure means someone else holds the lock.
I removed the part of the manual I had written which said that it will
raise an error if the platform it's running doesn't have any locking
primitive.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2006-05-24 21:35:02 | Re: file-locking and postmaster.pid |
| Previous Message | Tom Lane | 2006-05-24 21:33:02 | Re: file-locking and postmaster.pid |