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

From Josh Kupershmidt
Subject Re: foreign table: WARNING: problem in alloc set ExecutorState detected write past chunk end in block ...
Date
Msg-id CAK3UJRGs0kgJRYYLEEOwB98nc-Y5KNzp6uVa+FWJ8=f-XpmAGg@mail.gmail.com
Whole thread Raw
In response to Re: foreign table: WARNING: problem in alloc set ExecutorState detected write past chunk end in block ...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Sep 13, 2011 at 7:38 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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 ...

D'oh. Looks like this was a false alarm; I think I neglected to
recompile file_fdw.so to correspond to the server I was running. At
least, the warning has gone away upon a rebuild of the file_fdw
module. Sorry for the noise.

Josh


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs)
Next
From: Robert Haas
Date:
Subject: Re: DBI-LINK not support special support?