Re: Huge amount of memory errors with libpq

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Casey Jones <jonescaseyb(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Huge amount of memory errors with libpq
Date: 2010-09-12 22:44:26
Message-ID: 16053.1284331466@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Casey Jones <jonescaseyb(at)gmail(dot)com> writes:
> I don't think valgrind is the only issue here because outside valgrind my
> data is getting magically overwritten. In the function causing that problem
> I set all the fields I wanted to set by hand instead of using PQgetvalue().
> If I leave PQexec() uncommented, my data in a totally unrelated area would
> change, but when I comment it out I get the expected results. There might
> be an error I'm making thats causing this, but I can't find it in valgrind
> because of the huge number of errors.

FWIW, that test case shows no errors at all for me, on an x86_64 running
Fedora 13. I'd suggest trying it on something other than Gentoo.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Yaroslav Tykhiy 2010-09-12 23:36:35 Query plan choice issue
Previous Message sunpeng 2010-09-12 20:48:59 Re: why can't see the updated value after SPI_execute("update ....", false, 1);