Re: wCTE cannot be used to update parent inheritance table

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Geoghegan <peter(at)2ndquadrant(dot)com>
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 20:52:12
Message-ID: 11927.1327870332@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Peter Geoghegan <peter(at)2ndquadrant(dot)com> writes:
> On 29 January 2012 20:39, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>> Huh? I don't follow you at all Peter.

> I mean that we should change code like this:
> elog(ERROR, "could not find plan for CTE \"%s\"", rte->ctename)
> to this:
> elog(INTERNAL_ERROR, "could not find plan for CTE \"%s\"", rte->ctename)

Seems like a lot of make-work. The fact that it's got an XX000 SQLSTATE
is already sufficient confirmation that the problem is an internal one,
if the DBA isn't sure about that already.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2012-01-29 20:53:25 Re: wCTE cannot be used to update parent inheritance table
Previous Message Peter Geoghegan 2012-01-29 20:49:01 Re: wCTE cannot be used to update parent inheritance table