Re: Improving backend startup interlock

From: Giles Lean <giles(at)nemeton(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Improving backend startup interlock
Date: 2002-09-29 02:58:53
Message-ID: 15987.1033268333@nemeton.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Tom Lane wrote:

> Giles Lean <giles(at)nemeton(dot)com(dot)au> writes:
> > Is there some reason that file locking is not acceptable? Is there
> > any platform or filesystem supported for use with PostgreSQL which
> > doesn't have working exclusive file locking?
>
> How would we know? We have never tried to use such a feature.

I asked because I've not been following this project long enough to
know if it had been tried and rejected previously. Newcomers being
prone to making silly suggestions and all that. :-)

> For sure I would not trust it on an NFS filesystem. (Although we
> disparage running an NFS-mounted database, people do it anyway.)

<scratches head>

I can't work out if that's an objection or not.

I'm certainly no fan of NFS locking, but if someone trusts their NFS
client and server implementations enough to put their data on, they
might as well trust it to get a single lock file for startup right
too. IMHO. Your mileage may vary.

Regards,

Giles

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-09-29 03:06:07 Re: Improving backend startup interlock
Previous Message Tom Lane 2002-09-29 02:58:33 Re: [PATCHES] Cascaded Column Drop