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

From Michael Paquier
Subject Re: orangutan seizes up during isolation-check
Date
Msg-id CAB7nPqQE6A16MRn=1=JwTiNUyHx0NMRFHyZFqWsDgdGhYsBRxA@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
List pgsql-hackers
On Fri, Jan 2, 2015 at 1:04 PM, Noah Misch <noah@leadboat.com> wrote:
> The first attached patch, for all branches, adds LOG-level messages and an
> assertion.  So cassert builds will fail hard, while others won't.  The second
> patch, for master only, changes the startup-time message to FATAL.  If we
> decide to use FATAL in all branches, I would just squash them into one.

+           errdetail("Please report this to <pgsql-bugs@postgresql.org>.")));
Er, is mentioning a mailing list in an error message really necessary?
-- 
Michael



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: The return value of allocate_recordbuf()
Next
From: Noah Misch
Date:
Subject: Re: orangutan seizes up during isolation-check