| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_ctl configurable timeout |
| Date: | 2007-10-29 21:05:39 |
| Message-ID: | 6407.1193691939@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Bruce Momjian wrote:
>> How about an environment variable to control the timeout? Is that
>> cleaner?
> I don't see why it should be. I think Peter's --timeout suggestion
> should be just fine.
I wrote a moment ago that the user can hit control-C when he gets bored,
but that argument only works for interactive use of pg_ctl. In a script
I think you'd want a --timeout option. I don't see the advantage of
an environment variable in either scenario.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-10-29 21:07:32 | Re: pg_ctl configurable timeout |
| Previous Message | Alvaro Herrera | 2007-10-29 20:34:45 | Re: pg_ctl configurable timeout |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-10-29 21:07:32 | Re: pg_ctl configurable timeout |
| Previous Message | Alvaro Herrera | 2007-10-29 20:34:45 | Re: pg_ctl configurable timeout |