Re: foreign table: WARNING: problem in alloc set ExecutorState detected write past chunk end in block ... - Mailing list pgsql-hackers

From Tom Lane
Subject Re: foreign table: WARNING: problem in alloc set ExecutorState detected write past chunk end in block ...
Date
Msg-id 15356.1315957138@sss.pgh.pa.us
Whole thread Raw
In response to Re: foreign table: WARNING: problem in alloc set ExecutorState detected write past chunk end in block ...  (Josh Kupershmidt <schmiddy@gmail.com>)
Responses Re: foreign table: WARNING: problem in alloc set ExecutorState detected write past chunk end in block ...
List pgsql-hackers
Josh Kupershmidt <schmiddy@gmail.com> writes:
> On Tue, Sep 13, 2011 at 6:29 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Can't reproduce that here, on either 32-bit or 64-bit hardware.
>> However, this sort of issue is often exceedingly sensitive to
>> environment and build options. �What's your platform, what did you use
>> for configure options, etc?

> I got the warning on OS X 10.6 64-bit. The only configure options I
> used were --prefix=/path/ --enable-cassert --enable-debug.

Hmm.  I tried on 64-bit Lion (10.7.1) and had no luck.

Please try setting a gdb breakpoint on the warning elog (it's in aset.c)
and looking to see what's the contents of the complained-of chunk.  That
might give us a hint anyway ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Josh Kupershmidt
Date:
Subject: Re: foreign table: WARNING: problem in alloc set ExecutorState detected write past chunk end in block ...
Next
From: Tom Lane
Date:
Subject: Re: New releases for back branches 8.4 and 9.0?