Skip site navigation (1) Skip section navigation (2)

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-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>

  + If your life is a hard drive, Christ can be your backup. +

Attachment: /pgpatches/pg_ctl
Description: text/x-diff (6.3 KB)

In response to

pgsql-hackers by date

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

pgsql-patches by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group