From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
Subject: | Re: [HACKERS] pg_ctl configurable timeout |
Date: | 2007-11-10 21:53:36 |
Message-ID: | 200711102153.lAALraS08951@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
bruce wrote:
> Tom Lane wrote:
> > 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.
>
> I have implemented pg_ctl -t secs timeout option with the attached
> patch. It still defaults to 60. I did not code the 'ping' option.
Modified patch applied.
--
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. +
Attachment | Content-Type | Size |
---|---|---|
/rtmp/diff | text/x-diff | 8.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-11-10 22:44:25 | Re: tsearch2api .. wrapper for integrated fultext |
Previous Message | Pavel Stehule | 2007-11-10 20:20:52 | Re: tsearch2api .. wrapper for integrated fultext |