The following bug has been logged on the website:
Bug reference: 6408
Logged by: YAMAMOTO Takashi
Email address: y...@mwd.biglobe.ne.jp
PostgreSQL version: Unsupported/Unknown
Operating system: NetBSD
Description:
hi,
the following patch fixes/updates/adds random co
On Tue, Jan 24, 2012 at 4:03 PM, Tom Lane wrote:
> Phil Sorber writes:
>> On Tue, Jan 24, 2012 at 12:43 AM, Tom Lane wrote:
>>> How about a test case?
>
>> We are having trouble coming up with a test case that can reliably
>> reproduce this.
>
> The stack traces run through the EvalPlanQual mach
I screwed up cut and paste when putting the test case together. The
reference to table user_data should be t1.
On Wed, Jan 25, 2012 at 12:47 PM, Phil Sorber wrote:
> On Tue, Jan 24, 2012 at 4:03 PM, Tom Lane wrote:
>> Phil Sorber writes:
>>> On Tue, Jan 24, 2012 at 12:43 AM, Tom Lane wrote:
>>
Hi Vik,
On Wed, Jan 25, 2012 at 12:28 AM, Vik Reykja wrote:
> On Tue, Jan 24, 2012 at 14:41, Giuseppe Sucameli
> wrote:
>>
>> > I would try to cook up a patch but I have no skills :-(
>>
>> I'm going to write a patch to fix this problem.
>
> I managed to put something together and have posted it
Phil Sorber writes:
> That helped a lot. I now have a simple test case that I can reliably
> re-produce the segfault and now also a patch that fixes it.
[ pokes at that... ] Hmm. I think what this proves is that that
optimization in EvalPlanQualStart is just too cute for its own good,
and that
SEVERITY: normal
TYPE: SQL feature
VERSION TESTED: 9.1.2
PLATFORM: Ubuntu Linux, installed from apt-get
REPRODUCEABLE: 100%
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 n
