From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: wCTE cannot be used to update parent inheritance table |
Date: | 2012-01-29 22:11:34 |
Message-ID: | CAEYLb_Wv5dwVCoyVmjkU1MM=jfo9OgyRvPnVsUxbVDHHNjCpoA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 29 January 2012 21:19, Peter Geoghegan <peter(at)2ndquadrant(dot)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(at)commandprompt(dot)com> wrote:
>
> 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.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2012-01-29 22:42:35 | Silly typo in proc.h |
Previous Message | Tom Lane | 2012-01-29 21:33:13 | Re: BUG #6416: Expression index not used with UNION ALL queries |