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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [HACKERS] Patching dblink.c to avoid warning about open transaction
Дата
Msg-id 5021.1128700793@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [HACKERS] Patching dblink.c to avoid warning about open  (Bruce Momjian <pgman@candle.pha.pa.us>)
Ответы Re: [HACKERS] Patching dblink.c to avoid warning about open  (Bruce Momjian <pgman@candle.pha.pa.us>)
Список pgsql-patches
Bruce Momjian <pgman@candle.pha.pa.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

В списке pgsql-patches по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: [HACKERS] Patching dblink.c to avoid warning about open
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: [HACKERS] Patching dblink.c to avoid warning about open