Re: [HACKERS] pg_ctl configurable timeout

2007-11-05 Thread Alvaro Herrera
Tom Lane wrote: Alvaro Herrera [EMAIL PROTECTED] writes: I think the mythical pg_ping utility should be written. It seems the easiest way out of the problem. If pg_ctl were still a shell script there would be some point in that, but since it's a C program it can certainly do anything a

Re: [HACKERS] pg_ctl configurable timeout

2007-11-05 Thread Tom Lane
Alvaro Herrera [EMAIL PROTECTED] writes: Tom Lane wrote: Alvaro Herrera [EMAIL PROTECTED] writes: I think the mythical pg_ping utility should be written. It seems the easiest way out of the problem. If pg_ctl were still a shell script there would be some point in that, but since it's a C

Re: [HACKERS] pg_ctl configurable timeout

2007-10-29 Thread Peter Eisentraut
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.

Re: [HACKERS] pg_ctl configurable timeout

2007-10-29 Thread Andrew Dunstan
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. cheers andrtew ---(end of broadcast)--- TIP 4:

Re: [HACKERS] pg_ctl configurable timeout

2007-10-29 Thread Tom Lane
Peter Eisentraut [EMAIL PROTECTED] writes: 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

Re: [HACKERS] pg_ctl configurable timeout

2007-10-29 Thread Tom Lane
Andrew Dunstan [EMAIL PROTECTED] 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

Re: [HACKERS] pg_ctl configurable timeout

2007-10-29 Thread Tom Lane
Alvaro Herrera [EMAIL PROTECTED] writes: I think the mythical pg_ping utility should be written. It seems the easiest way out of the problem. If pg_ctl were still a shell script there would be some point in that, but since it's a C program it can certainly do anything a separate utility would

Re: [HACKERS] pg_ctl configurable timeout

2007-10-29 Thread Simon Riggs
On Mon, 2007-10-29 at 17:34 -0300, Alvaro Herrera wrote: Maybe hack the postmaster to have a new special connection mode which keeps the connection open until the startup process exits, to avoid polling continuously (ideally report progress too, if at all possible). That sounds good to me.

Re: [HACKERS] pg_ctl configurable timeout

2007-10-29 Thread Alvaro Herrera
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

Re: [HACKERS] pg_ctl configurable timeout

2007-10-29 Thread Bruce Momjian
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

Re: [HACKERS] pg_ctl configurable timeout

2007-10-29 Thread Dave Page
--- Original Message --- From: Peter Eisentraut [EMAIL PROTECTED] To: pgsql-hackers@postgresql.org Sent: 29/10/07, 17:54:00 Subject: Re: [HACKERS] pg_ctl configurable timeout Am Freitag, 17. August 2007 schrieb Peter Eisentraut: I'm having trouble with the hardcoded 60 second

Re: [HACKERS] pg_ctl configurable timeout

2007-08-23 Thread Zdenek Kotala
Peter Eisentraut wrote: 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? +1 I played with

Re: [HACKERS] pg_ctl configurable timeout

2007-08-23 Thread Joshua D. Drake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zdenek Kotala wrote: Peter Eisentraut wrote: 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

Re: [HACKERS] pg_ctl configurable timeout

2007-08-23 Thread Zdenek Kotala
Joshua D. Drake wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zdenek Kotala wrote: Peter Eisentraut wrote: 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

[HACKERS] pg_ctl configurable timeout

2007-08-17 Thread 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? -- Peter Eisentraut