Skip site navigation (1) Skip section navigation (2)

Re: Re: [COMMITTERS] pgsql: Reserve the shared memory region during backend startup on

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Reserve the shared memory region during backend startup on
Date: 2009-07-28 13:45:57
Message-ID: 16359.1248788757@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Mon, Jul 27, 2009 at 16:14, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2009-07-28 14:28:46
Subject: Re: Review: Revise parallel pg_restore's scheduling heuristic
Previous:From: Peter EisentrautDate: 2009-07-28 13:13:10
Subject: Re: SE-PostgreSQL Specifications

pgsql-committers by date

Next:From: Teodor SigaevDate: 2009-07-28 13:46:58
Subject: Re: pgsql: Correct calculations of overlap and contains operations over
Previous:From: Robert HaasDate: 2009-07-28 13:04:32
Subject: Re: pgsql: Correct calculations of overlap and contains operations over

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group