From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_ctl configurable timeout |
Date: | 2007-10-29 20:06:23 |
Message-ID: | 200710292006.l9TK6NW23296@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
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?
How about an environment variable to control the timeout? Is that
cleaner?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-10-29 20:16:17 | Re: pg_ctl configurable timeout |
Previous Message | Dave Page | 2007-10-29 20:00:49 | Re: pg_ctl configurable timeout |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2007-10-29 20:16:17 | Re: pg_ctl configurable timeout |
Previous Message | Peter Eisentraut | 2007-10-29 16:54:00 | Re: pg_ctl configurable timeout |