Re: BUG #16466: Valgrind detects an invalid read in dblink_open()with a cursor inside a transaction - Mailing list pgsql-bugs

From Joe Conway
Subject Re: BUG #16466: Valgrind detects an invalid read in dblink_open()with a cursor inside a transaction
Date
Msg-id 3e6699ba-3896-a641-0c95-b64069d77a73@joeconway.com
Whole thread Raw
In response to Re: BUG #16466: Valgrind detects an invalid read in dblink_open()with a cursor inside a transaction  (Alexander Lakhin <exclusion@gmail.com>)
List pgsql-bugs
On 5/27/20 5:00 PM, Alexander Lakhin wrote:
> Hello Joe,
>
> 27.05.2020 22:58, Joe Conway wrote:
>> Hmmm, looks like a couple of the members of rconn are left uninitialized.
>>
>> When dblink_open() is called *without* an outer transaction it handles the
>> initialization for us, but *with* an outer transaction it does not :-(
>>
>> I think the attached fixes it.
> Yes, your patch makes valgrind silent.
> Thanks!


Thanks for checking! Pushed to all supported branches.

Joe

--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development


Attachment

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgbench bug / limitation
Next
From: James Lucas
Date:
Subject: Re: Explicit deterministic COLLATE fails with pattern matchingoperations on column with non-deterministic collation