On Wed, Jun 8, 2011 at 10:18 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Merlin Moncure <mmonc...@gmail.com> writes: >> I went ahead and tested andrew's second patch -- can we get this >> reviewed and committed? > > Add it to the upcoming commitfest.
It's a client crashing bug in PQsetvalue that goes back to 9.0 :(. In short (apologies for the non-context diff), PQsetvalue was inappropriately using libpq tuple slots as a check to see if it should allocate the per row tuple datums, and borked when setting values on a non copied result (libpqtypes always copies results) because the regular pqAddTuple does not null out the slots like copy result does. The whole mechanism was basically unnecessary, so it was removed, fixing the bug. merlin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
