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 ) id 1oGNCT-0001e9-3V for pgsql-bugs@arkaria.postgresql.org; Tue, 26 Jul 2022 16:14:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oGNCR-0005Ql-TR for pgsql-bugs@arkaria.postgresql.org; Tue, 26 Jul 2022 16:14:23 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oGNCR-0005Qc-Lc for pgsql-bugs@lists.postgresql.org; Tue, 26 Jul 2022 16:14:23 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oGNCP-0007fI-Ac for pgsql-bugs@lists.postgresql.org; Tue, 26 Jul 2022 16:14:22 +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 26QGEJio2363213; Tue, 26 Jul 2022 12:14:19 -0400 From: Tom Lane To: "David G. Johnston" cc: Bruce Momjian , Yugo Nagata , PostgreSQL mailing lists Subject: Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands In-reply-to: References: <17434-d9f7a064ce2a88a3@postgresql.org> <3190751.1657845414@sss.pgh.pa.us> <3498921.1657919211@sss.pgh.pa.us> <805866.1658175624@sss.pgh.pa.us> <2350990.1658848101@sss.pgh.pa.us> <2356216.1658849834@sss.pgh.pa.us> <2361330.1658851386@sss.pgh.pa.us> Comments: In-reply-to "David G. Johnston" message dated "Tue, 26 Jul 2022 09:11:52 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2363211.1658852059.1@sss.pgh.pa.us> Date: Tue, 26 Jul 2022 12:14:19 -0400 Message-ID: <2363212.1658852059@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "David G. Johnston" writes: > And we are back around to the fact that only by using libpq directly, or > via the pipeline feature of pgbench, can one actually exert control over > the implicit transaction. The psql and general SQL interface > implementation are just going to Sync after each command and so everything > looks like one transaction per command to them and only explicit > transactions matter. Right. > From that, the adjustment you describe above is sufficient for me. Cool, I'll set about back-patching. regards, tom lane