Re: [HACKERS] Patching dblink.c to avoid warning about open transaction

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Joe Conway <mail(at)joeconway(dot)com>, David Fetter <david(at)fetter(dot)org>, Jonathan Beit-Aharon <jbeitaharon(at)intrusic(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [HACKERS] Patching dblink.c to avoid warning about open transaction
Date: 2005-10-07 15:59:53
Message-ID: 5021.1128700793@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> The problem with not using rconn is that we are not saving the
> transaction status at the _start_ of the cursor open. If we don't do
> that, we have no way of knowing on close if _we_ opened the transaction
> or whether it was opened by the user.

Oh, I see. In that case the flag is horribly misnamed and miscommented.
Something like "newXactForCursor" would be clearer.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-10-07 16:05:16 Re: [HACKERS] Patching dblink.c to avoid warning about open
Previous Message Tom Lane 2005-10-07 15:56:50 Re: Vote needed: revert beta2 changes or not?

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2005-10-07 16:05:16 Re: [HACKERS] Patching dblink.c to avoid warning about open
Previous Message Bruce Momjian 2005-10-07 15:50:27 Re: [HACKERS] Patching dblink.c to avoid warning about open