From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: In 8.2, shutdown wrongly caused automatic restart |
Date: | 2010-08-04 16:45:46 |
Message-ID: | 1280940285-sup-9807@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Excerpts from Tom Lane's message of mié ago 04 12:37:23 -0400 2010:
> Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
> > 6. ... the bgwriter had already ended even though there was a backend in
> > progress. Postmaster regarded this situation as abnormal and caused the
> > recovery.
>
> > In 8.3 or later, since postmaster doesn't regard that situation as abnormal
> > and just waits for all backends to exit again, the problem doesn't happen.
> > I think that this is a bug in 8.2 and should be fixed in the same way as 8.3
> > does. Thought?
>
> My recollection is that that change was associated with some pretty
> significant revisions to the postmaster state machine. I'm concerned
> about the risks involved in back-patching that. This seems to be a
> corner case with pretty minimal consequences anyway, so I'm inclined
> to leave 8.2 alone.
IIRC this is the kind of thing that "dead-end backends" were invented
for. It was too a large patch for backpatching, IMHO.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-08-04 16:50:53 | Re: string_agg delimiter having no effect with order by |
Previous Message | Tom Lane | 2010-08-04 16:44:40 | Re: string_agg delimiter having no effect with order by |