Re: In 8.2, shutdown wrongly caused automatic restart

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: In 8.2, shutdown wrongly caused automatic restart
Date: 2010-08-06 06:16:08
Message-ID: AANLkTimDb7Zin034LjXw40HARoVNLVf7w7E6Zth-T98D@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Aug 5, 2010 at 1:45 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Excerpts from Tom Lane's message of mié ago 04 12:37:23 -0400 2010:
>> 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.

Though I thought about this issue for a while, I end up agreeing that
the back-patching has a risk.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Adam Radlowski 2010-08-06 08:12:08 BUG #5605: round(attr_name,int) works bad
Previous Message Jon Erdman (aka StuckMojo) 2010-08-06 04:31:46 BUG #5604: Setting NOT NULL on inherited column turns to real column in dump