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

From: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-14 22:22:59
Message-ID: CAK3UJRGs0kgJRYYLEEOwB98nc-Y5KNzp6uVa+FWJ8=f-XpmAGg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 13, 2011 at 7:38 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-09-15 03:47:21 Re: DBI-LINK not support special support?
Previous Message Robert Haas 2011-09-14 20:29:31 memory barriers (was: Yes, WaitLatch is vulnerable to weak-memory-ordering bugs)