Re: orangutan seizes up during isolation-check - Mailing list pgsql-hackers

From Robert Haas
Subject Re: orangutan seizes up during isolation-check
Date
Msg-id CA+TgmoYQ6pPNDokUz9BGeNCms9kupFx=RuLjoaSwbxTyLz6V8w@mail.gmail.com
Whole thread Raw
In response to Re: orangutan seizes up during isolation-check  (Noah Misch <noah@leadboat.com>)
Responses Re: orangutan seizes up during isolation-check  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
On Sun, Dec 28, 2014 at 4:58 PM, Noah Misch <noah@leadboat.com> wrote:
> I wondered whether to downgrade FATAL to LOG in back branches.  Introducing a
> new reason to block startup is disruptive for a minor release, but having the
> postmaster deadlock at an unpredictable later time is even more disruptive.  I
> am inclined to halt startup that way in all branches.

Jeepers.  I'd rather not do that.  From your report, this problem has
been around for years.  Yet, as far as I know, it's bothering very few
real users, some of whom might be far more bothered by the postmaster
suddenly failing to start.  I'm fine with a FATAL in master, but I'd
vote against doing anything that might prevent startup in the
back-branches without more compelling justification.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Using 128-bit integers for sum, avg and statistics aggregates
Next
From: Guillaume Lelarge
Date:
Subject: Re: BUG: *FF WALs under 9.2 (WAS: .ready files appearing on slaves)