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: Bruce Momjian <pgman(at)candle(dot)pha(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-04 19:58:06
Message-ID: Pine.LNX.4.21.0007042130110.3542-100000@localhost.localdomain (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Bruce Momjian writes:

> > On Tue, 4 Jul 2000, Bruce Momjian - CVS wrote:
> > 
> > > Removed Files:
> > > 	alpha default distinct flock fsync function limit null 
> > > 	pg_shadow primary 
> > 
> > What are we going to do with the flock? Remove it? I asked about this
> > yesterday, I guess it's not useful anymore.
> 
> Well, we have the postmaster pid thing working now.  Is there an issue
> with flock() I have forgotten?

We still have the locking code in there, together with the broken
configure test. See my message from the other day ("fcntl(F_SETLK)") --
should we just remove all that stuff?


-- 
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: Tom LaneDate: 2000-07-04 20:11:15
Subject: Re: zlib for pg_dump
Previous:From: Peter EisentrautDate: 2000-07-04 19:57:52
Subject: Dumping SQL type names

pgsql-committers by date

Next:From: Peter EisentrautDate: 2000-07-05 00:12:15
Subject: Re: [COMMITTERS] pgsql/doc/TODO.detail (alpha default distinct flock fsync function limit null pg_shadow primary)
Previous:From: Peter EisentrautDate: 2000-07-04 19:57:37
Subject: Re: Memory-context slinging

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