Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: file-locking and postmaster.pid
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: korry(at)appx(dot)com
- Cc: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: file-locking and postmaster.pid
- Date: Wed, 24 May 2006 17:46:00 -0400
- Message-id: <2445(dot)1148507160(at)sss(dot)pgh(dot)pa(dot)us>
korry <korry(at)appx(dot)com> writes: > What we currently have in place is not bulletproof. Well, it fails in the safe direction: the postmaster may occasionally refuse to start when it should, but it won't ever start when it should not. It appears to me that anything relying on file locking will tend to fail in the other direction, and that's not acceptable IMHO. regards, tom lane
- Follow-Ups:
- Re: file-locking and postmaster.pid
- From: korry
- Re: file-locking and postmaster.pid
- References:
- file-locking and postmaster.pid
- From: Andreas Joseph Krogh
- Re: file-locking and postmaster.pid
- From: korry
- Re: file-locking and postmaster.pid
- From: Andreas Joseph Krogh
- Re: file-locking and postmaster.pid
- From: korry
- Re: file-locking and postmaster.pid
- From: Alvaro Herrera
- Re: file-locking and postmaster.pid
- From: Tom Lane
- Re: file-locking and postmaster.pid
- From: korry
- file-locking and postmaster.pid
- Prev by Date: Re: Compression and on-disk sorting
- Next by Date: Re: compiling source code!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
- Previous by thread: Re: file-locking and postmaster.pid
- Next by thread: Re: file-locking and postmaster.pid
- Indexes: