Re: pg_ctl configurable timeout

Peter Eisentraut wrote:
> 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?

I think the mythical pg_ping utility should be written.  It seems the
easiest way out of the problem.

Maybe hack the postmaster to have a new special connection mode which
keeps the connection open until the startup process exits, to avoid
polling continuously (ideally report progress too, if at all possible).

-- 
Alvaro Herrera                 http://www.amazon.com/gp/registry/DXLWNGRJD34J
Y dijo Dios: "Que sea Satanás, para que la gente no me culpe de todo a mí."
"Y que hayan abogados, para que la gente no culpe de todo a Satanás"