Phil Sorber writes:
> On Wed, Jan 25, 2012 at 5:13 PM, Tom Lane wrote:
> I played around with removing the optimization, but there are other
> pieces further down the line that are upset but having a ModifyTable
> node in the execution tree.
Hm, yeah, obviously this scenario has never been teste
On Wed, Jan 25, 2012 at 5:13 PM, Tom Lane wrote:
> 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 Eva
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
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:
>>
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
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 machinery, which is only
going to be entered when attempting to
On Tue, Jan 24, 2012 at 12:43 AM, Tom Lane wrote:
> Phil Sorber writes:
>> I've attached a backtrace.
>
> How about a test case? I have no faith in the proposed patch without
> some evidence of what it's supposed to fix.
We are having trouble coming up with a test case that can reliably
reprodu
Phil Sorber writes:
> I've attached a backtrace.
How about a test case? I have no faith in the proposed patch without
some evidence of what it's supposed to fix.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your s