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

Re: pg_ctl configurable timeout

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_ctl configurable timeout
Date: 2007-10-29 16:54:00
Message-ID: 200710291754.01494.peter_e@gmx.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Am Freitag, 17. August 2007 schrieb Peter Eisentraut:
> I'm having trouble with the hardcoded 60 second timeout in pg_ctl.  pg_ctl
> sometimes just times out and there is no way to make it wait a little
> longer. I would like to add an option to be able to change that, say
> pg_ctl -w --timeout=120.  Comments?

Lost track of this, but it keeps biting me.

Somehow, the 60 second timeout seems completely arbitrary anyway.  Maybe we 
should remove it altogether.  We could add an option as described above, but 
then the packager who creates the init script or whoever creates the initial 
configuration will have to make an equally arbitrary choice.  And most likely 
you will not notice that your configuration is insufficient until you are 
really in a bind.

What should we do?

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Responses

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2007-10-29 17:17:09
Subject: Re: [HACKERS] WAL archiving idle database
Previous:From: Jeff DavisDate: 2007-10-29 16:50:15
Subject: Re: [HACKERS] WAL archiving idle database

pgsql-patches by date

Next:From: Bruce MomjianDate: 2007-10-29 20:06:23
Subject: Re: pg_ctl configurable timeout
Previous:From: Peter EisentrautDate: 2007-10-29 10:05:22
Subject: Re: mingw autoconf again

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