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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-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/
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2007-10-29 17:17:09 | Re: [HACKERS] WAL archiving idle database |
Previous Message | Jeff Davis | 2007-10-29 16:50:15 | Re: [HACKERS] WAL archiving idle database |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-10-29 20:06:23 | Re: pg_ctl configurable timeout |
Previous Message | Peter Eisentraut | 2007-10-29 10:05:22 | Re: mingw autoconf again |