Re: wCTE cannot be used to update parent inheritance table

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Peter Geoghegan <peter(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: wCTE cannot be used to update parent inheritance table
Date: 2012-01-29 23:47:54
Message-ID: 4F25DAAA.5060008@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


>>> 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.

This is *so* not a discussion to have on the pgsql-bugs list. Please
take it to -hackers.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2012-01-29 23:52:30 Re: wCTE cannot be used to update parent inheritance table
Previous Message Peter Geoghegan 2012-01-29 22:42:35 Silly typo in proc.h