| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, davec(at)postgresintl(dot)com, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Subject: | Re: orangutan seizes up during isolation-check |
| Date: | 2015-01-05 06:02:36 |
| Message-ID: | 20150105060236.GA2300592@tornado.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 05, 2015 at 02:25:09PM +0900, Michael Paquier wrote:
> On Fri, Jan 2, 2015 at 1:04 PM, Noah Misch <noah(at)leadboat(dot)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(at)postgresql(dot)org>.")));
> Er, is mentioning a mailing list in an error message really necessary?
Necessary? No.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2015-01-05 06:19:28 | Typo in function header for recently added function errhidecontext |
| Previous Message | Michael Paquier | 2015-01-05 05:25:09 | Re: orangutan seizes up during isolation-check |