Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1p5Avk-0002kw-N2
	for pgsql-hackers@arkaria.postgresql.org; Tue, 13 Dec 2022 19:27:08 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1p5Avj-0002RZ-KE
	for pgsql-hackers@arkaria.postgresql.org; Tue, 13 Dec 2022 19:27:07 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1p5Avj-0002RQ-BM
	for pgsql-hackers@lists.postgresql.org; Tue, 13 Dec 2022 19:27:07 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1p5Avg-0007Tb-TS
	for pgsql-hackers@postgresql.org; Tue, 13 Dec 2022 19:27:06 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 2BDJQw8v2495272;
	Tue, 13 Dec 2022 14:26:59 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
cc: Israel Barth Rubio <barthisrael@gmail.com>,
        Yugo NAGATA <nagata@sraoss.co.jp>, pgsql-hackers@postgresql.org,
        "David G. Johnston" <david.g.johnston@gmail.com>,
        Bruce Momjian <bruce@momjian.us>
Subject: Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same
 transaction with other commands
In-reply-to: <2207596.1670880178@sss.pgh.pa.us>
References: <17434-d9f7a064ce2a88a3@postgresql.org>
 <805866.1658175624@sss.pgh.pa.us>
 <CAKFQuwYQpm6E4nTgiOZAGRg0JKquHaXQ0JkqruWeHuOQX6-70g@mail.gmail.com>
 <2350990.1658848101@sss.pgh.pa.us>
 <CAKFQuwYRYhF8iOD9MHp7VuZur_JvVEjDzpMHuUHNeYReB5v2Sw@mail.gmail.com>
 <2356216.1658849834@sss.pgh.pa.us>
 <CAKFQuwYxPhPVMGJ-uoV7rq291xAU3dwww2fWwMuaz6EPiruJ5g@mail.gmail.com>
 <2361330.1658851386@sss.pgh.pa.us>
 <CAKFQuwYaN+SJyHcXyjAwZ7zRCze+6Xj7ns_hOEg2+fhZEJUOHg@mail.gmail.com>
 <2363212.1658852059@sss.pgh.pa.us>
 <20220728105134.d5ce51dd756b3149e9b9c52c@sraoss.co.jp>
 <3214515.1658976655@sss.pgh.pa.us>
 <20220809002102.b815cd4dad20fdc91dff5ce8@sraoss.co.jp>
 <65a899dd-aebc-f667-1d0a-abb89ff3abf8@enterprisedb.com>
 <3995893.1668011885@sss.pgh.pa.us>
 <20221110144859.d9004fdd47396fe64fe032da@sr! aoss.co.jp>
 <229552.1668112417@sss.pgh.pa.us>
 <CAO_rXXCqRiPLWjAKxP5P4RfTHWhwn-eo-uZeURib1umQSaEoag@mail.gmail.com>
 <4066263.1669395975@sss.pgh.pa.us>
 <be36e954-b343-decf-69b9-8850f3acafef@enterprisedb.com> !
 <2207596.1670880178@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Mon, 12 Dec 2022 16:22:58 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2495270.1670959618.1@sss.pgh.pa.us>
Date: Tue, 13 Dec 2022 14:26:58 -0500
Message-ID: <2495271.1670959618@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: 
 <https://www.postgresql.org/message-id/2495271.1670959618%40sss.pgh.pa.us>
Precedence: bulk

I wrote:
> Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
>> 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.

> OK, I'll make this happen soon.

Pushed.  I left out the idea of making this conditional on whether
any preceding command had performed data modification, as that seemed
to greatly complicate the explanation (since "have we performed any
data modification" is a rather squishy question from a user's viewpoint).

			regards, tom lane