You are correct. It was my own fault.
Thanks for your time.
On Sun, 2004-01-11 at 15:42, Tom Lane wrote:
>
> This suggests to me that something has clobbered malloc's internal data
> structures. The most common cause of such an error is writing past the
> end of a memory block obtained from malloc; other likely causes are
> writing on already-freed memory, and ye ever-popular plain old wild store.
>
>
> I think it much more likely to be a bug in your surrounding program.
> If you can provide a simple test case that reproduces the problem,
> though, we can investigate the possibility of a bug in libpq.
--
Tor Gunston <tor@tor.to>