Re: wCTE cannot be used to update parent inheritance table - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: wCTE cannot be used to update parent inheritance table
Date
Msg-id CAEYLb_Wv5dwVCoyVmjkU1MM=jfo9OgyRvPnVsUxbVDHHNjCpoA@mail.gmail.com
Whole thread Raw
In response to Re: wCTE cannot be used to update parent inheritance table  (Peter Geoghegan <peter@2ndquadrant.com>)
Responses Re: wCTE cannot be used to update parent inheritance table  (Josh Berkus <josh@agliodbs.com>)
List pgsql-bugs
On 29 January 2012 21:19, Peter Geoghegan <peter@2ndquadrant.com> wrote:
> Is it really that much of a problem to create a new severity level for
> this stuff?

I should probably have quoted this refinement, which was part of the
discussion that I originally quoted Robert from:

On 24 November 2011 16:55, Alvaro Herrera <alvherre@commandprompt.com> wrot=
e:
>
> Excerpts from Robert Haas's message of jue nov 24 13:14:38 -0300 2011:
>
>> What I think we want to distinguish between is things that are
>> PEBKAC/GIGO, and everything else.  In other words, if a particular
>> error message can be caused by typing something stupid, unexpected,
>> erroneous, or whatever into psql, it's just an error.  But if no
>> input, however misguided, should ever cause that symptom, then it's, I
>> don't know what the terminology should be, say, a "severe error".
>
> +1

I'm strongly in favour of this.

--=20
Peter Geoghegan =A0 =A0 =A0 http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #6416: Expression index not used with UNION ALL queries
Next
From: Peter Geoghegan
Date:
Subject: Silly typo in proc.h