Re: foreign table: WARNING: problem in alloc set ExecutorState detected write past chunk end in block ...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: foreign table: WARNING: problem in alloc set ExecutorState detected write past chunk end in block ...
Date: 2011-09-13 23:38:58
Message-ID: 15356.1315957138@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Kupershmidt <schmiddy(at)gmail(dot)com> writes:
> On Tue, Sep 13, 2011 at 6:29 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-09-14 00:28:05 Re: New releases for back branches 8.4 and 9.0?
Previous Message Josh Kupershmidt 2011-09-13 23:22:19 Re: foreign table: WARNING: problem in alloc set ExecutorState detected write past chunk end in block ...