Re: BUG #16466: Valgrind detects an invalid read in dblink_open() with a cursor inside a transaction

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Joe Conway <mail(at)joeconway(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16466: Valgrind detects an invalid read in dblink_open() with a cursor inside a transaction
Date: 2020-05-27 21:00:00
Message-ID: fb147109-0512-8dc7-5e29-7b4b89ed246e@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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!

Best regards,
Alexander

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-05-27 22:09:09 BUG #16467: XX000 fun
Previous Message Joe Conway 2020-05-27 19:58:24 Re: BUG #16466: Valgrind detects an invalid read in dblink_open() with a cursor inside a transaction