Re: Re: [COMMITTERS] pgsql: Reserve the shared memory region during backend startup on - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [COMMITTERS] pgsql: Reserve the shared memory region during backend startup on
Date
Msg-id 16359.1248788757@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Reserve the shared memory region during backend startup on  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Re: [COMMITTERS] pgsql: Reserve the shared memory region during backend startup on
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> On Mon, Jul 27, 2009 at 16:14, Tom Lane<tgl@sss.pgh.pa.us> wrote:
>> I'm not really insisting on a redesign. �I'm talking about the places
>> where the code author appears not to have understood that ERROR means
>> FATAL, because the code keeps plugging on after it anyway. �As far as
>> I can see, using ERROR at lines 3630, 3657, 3674, and 3693 is just
>> plain bogus, and changing to LOG there requires no other fixing.

> But. I'll look into cleaning those up for HEAD anyway, but due to lack
> of reports I think we should skip backpatch. Reasonable?

Fair enough.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: SE-PostgreSQL Specifications
Next
From: "Tao Ma"
Date:
Subject: question about the _SPI_save_plan() and plan cache