| From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(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 20:31:23 |
| Message-ID: | CAEYLb_UHPgHN38cNjgYuQJnacspS7edAhOWcf4Nghu0Q-8S7pQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 29 January 2012 20:06, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 1/28/12 5:27 PM, Tom Lane wrote:
>> Josh Berkus <josh(at)agliodbs(dot)com> writes:
>>> SUMMARY: if you attempt to UPDATE or DELETE FROM a parent table in an
>>> inheritance relationship using a wCTE, you get the following error message:
>>> ERROR: could not find plan for CTE
>>
>> Fixed, thanks for the report.
>
> Should we add a regression test for this?
This is the kind of thing that could go unnoticed for a long time,
simply because it is not highlighted any more prominently than a
routine error message like an integrity constraint violation. I
continue to maintain that we should have a new severity level for this
sort of thing.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2012-01-29 20:39:24 | Re: wCTE cannot be used to update parent inheritance table |
| Previous Message | Josh Berkus | 2012-01-29 20:06:55 | Re: wCTE cannot be used to update parent inheritance table |