Horton

Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, Israel Barth Rubio <barthisrael@gmail.com>
Cc: Yugo NAGATA <nagata@sraoss.co.jp>, pgsql-hackers@postgresql.org, "David G. Johnston" <david.g.johnston@gmail.com>, Bruce Momjian <bruce@momjian.us>
Date: 2022-12-12T19:16:32Z
Lists: pgsql-bugs, pgsql-hackers 
On 25.11.22 18:06, Tom Lane wrote:
> Israel Barth Rubio <barthisrael@gmail.com> writes:
>> It would be great if we can back-patch this to all supported versions,
>> as the issue itself is currently affecting them all.
> 
> In my mind, this is waiting for Peter to opine on whether it satisfies
> his concern.

The case I was working on is the same as Israel's.  He has confirmed 
that this fixes the issue we have been working on.

Commits

  1. Rethink handling of [Prevent|Is]InTransactionBlock in pipeline mode.

  2. Doc: add comments about PreventInTransactionBlock/IsInTransactionBlock.

  3. Force immediate commit after CREATE DATABASE etc in extended protocol.