Skip site navigation (1) Skip section navigation (2)

Re: [COMMITTERS] pgsql/doc/TODO.detail (alpha default distinct flock fsync function limit null pg_shadow primary)

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql/doc/TODO.detail (alpha default distinct flock fsync function limit null pg_shadow primary)
Date: 2000-07-05 00:12:15
Message-ID: Pine.LNX.4.21.0007042325530.3542-100000@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Tom Lane writes:

> but if one or both postmasters is started without -i then there's got
> to be some interlock on the Unix socket file.
> 
> I don't much like depending on flock for that, since it isn't available
> everywhere.  The only portable answer is to build a pid-containing
> interlock file for each socket file, as discussed in the TODO item.

But the flock code isn't used because the configure test for it is broken,
and has been broken ever since it was introduced AFAICT. It seems that we
have been relying on the mere existence of the socket file.


-- 
Peter Eisentraut                  Sernanders väg 10:115
peter_e(at)gmx(dot)net                   75262 Uppsala
http://yi.org/peter-e/            Sweden


In response to

Responses

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2000-07-05 00:12:24
Subject: Re: Changes to handling version numbers internally
Previous:From: Peter EisentrautDate: 2000-07-05 00:11:53
Subject: Re: Revised Copyright: is this more palatable?

pgsql-committers by date

Next:From: Tom LaneDate: 2000-07-05 00:25:53
Subject: Re: Memory-context slinging
Previous:From: Peter EisentrautDate: 2000-07-04 19:58:06
Subject: Re: [COMMITTERS] pgsql/doc/TODO.detail (alpha default distinct flock fsync function limit null pg_shadow primary)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group