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

Re: pid gets overwritten in OSX

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Francois Suter <dba(at)paragraf(dot)ch>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pid gets overwritten in OSX
Date: 2002-04-29 15:25:11
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-generalpgsql-hackers
Francois Suter <dba(at)paragraf(dot)ch> writes:
> Maybe there's some operation missing at shutdown. I installed 
> PostgreSQL using Mark Liyanage's package. Could there be something 
> missing? Is Postgres taking care of the removal of the 
> file or do you have to do it yourself in some shutdown script?

No, you shouldn't need to do it yourself.  The approved way to shut down
Pg is to send the postmaster a SIGTERM signal --- which I believe all
Unixen will do automatically during the shutdown sequence.  What may be
happening is that the system is not giving the postmaster a long enough
grace period between SIGTERM and hard kill.  We need a minimum of about
three seconds I believe (there's a 2-second sleep() in the checkpoint
sync code, which maybe should not be there, but it's there at the
moment).  Traditionally systems have allowed 10 seconds or more to
respond to SIGTERM, but perhaps Apple thought they could shave some
time there?

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Thomas LockhartDate: 2002-04-29 15:29:56
Subject: Re: Vote totals for SET in aborted transaction
Previous:From: Olivier PRENANTDate: 2002-04-29 15:14:20
Subject: clarification of timestamp

pgsql-general by date

Next:From: Steve LaneDate: 2002-04-29 15:35:56
Subject: Re: Postgres utils chewing RAM
Previous:From: Francois SuterDate: 2002-04-29 15:05:27
Subject: Re: pid gets overwritten in OSX

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