Re: [HACKERS] pg_ctl configurable timeout

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] pg_ctl configurable timeout
Date: 2007-11-10 05:06:15
Message-ID: 200711100506.lAA56FV11240@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

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.

--
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
/pgpatches/pg_ctl text/x-diff 6.3 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message rcolmegna@tiscali.it 2007-11-10 07:47:46 data access automatic filter
Previous Message Bruce Momjian 2007-11-10 03:55:15 Re: [BUGS] Nasty tsvector can make dumps unrestorable

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2007-11-10 14:37:38 Re: [HACKERS] Connection Pools and DISCARD ALL
Previous Message Joe Conway 2007-11-10 05:04:51 Re: [GENERAL] Crosstab Problems