From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org, Gerhard Leykam <gel123(at)sealsystems(dot)de> |
Subject: | Re: BUG #5118: start-status-insert-fatal |
Date: | 2009-10-15 17:41:01 |
Message-ID: | 20091015174101.GG4788@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Kevin Grittner wrote:
> This seems likely to overlap the review I was soon going to do of the
> differences between pg_ctl behavior and what is required for LSB
> conformance. I'll make sure to test this behavior along with others.
> One of my current complaints is that pg_ctl doesn't wait until it is
> actually ready to receive connections before returning an indication
> of success.
Maybe write the file as postmaster.ports.starting or some such and
rename it to its final name when recovery has finished?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Steven McLellan | 2009-10-15 17:50:23 | BUG #5120: Performance difference between running a query with named cursor and straight SELECT |
Previous Message | Tom Lane | 2009-10-15 17:34:15 | Re: BUG #5118: start-status-insert-fatal |