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

Re: We should Axe /contrib/start-scripts

From: Chander Ganesan <chander(at)otg-nc(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Aidan Van Dyk <aidan(at)highrise(dot)ca>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Josh Berkus <josh(at)agliodbs(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: We should Axe /contrib/start-scripts
Date: 2009-08-26 00:44:17
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane wrote:
> Aidan Van Dyk <aidan(at)highrise(dot)ca> writes:
>> Can postmaster keep a exclusive lock on its own pid file the entire time it's
>> running?
> That's been discussed, but file locking isn't all that portable or
> trustworthy :-(
> 			regards, tom lane
What about having a special request via the socket file asking for its 
data directory (not over the network)?  Or even to have it just update 
the timestamp on its pid file...

Chander Ganesan
Open Technology Group, Inc.
One Copley Parkway, Suite 210
Morrisville, NC  27560

In response to

pgsql-hackers by date

Next:From: WANGRUNGVICHAISRI, SHIVESHDate: 2009-08-26 01:25:50
Subject: Re: BUG #4996: postgres.exe memory consumption keeps going up
Previous:From: Tom LaneDate: 2009-08-26 00:22:16
Subject: Re: We should Axe /contrib/start-scripts

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