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 10009.1248704092@sss.pgh.pa.us
Whole thread Raw
In response to 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  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> To fix that we'd just have to turn those functions all into returning
> boolean and log with LOG instead. AFAIK, we've had zero reports of
> this actually happening, so I'm not sure it's worth redesigning.
> Thoughts?

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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Ahmed DERBAH"
Date:
Subject: FW: PostGres developer Contact
Next
From: Tom Lane
Date:
Subject: Re: [RFC] new digest datatypes, or generic fixed-len hex types?