From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: nagata@sraoss.co.jp
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
Date: Thu, 14 Jul 2022 20:36:54 -0400
Message-ID: <3190751.1657845414@sss.pgh.pa.us> (raw)
In-Reply-To: <YtCrjN0HLew0w4Ss@momjian.us>
References: <17434-d9f7a064ce2a88a3@postgresql.org>
<YtCrjN0HLew0w4Ss@momjian.us>
Bruce Momjian <bruce@momjian.us> writes:
> Did we make any decision on this?
Hmm, that one seems to have slipped past me. I agree it doesn't
look good. But why isn't the PreventInTransactionBlock() check
blocking the command from even starting?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, bruce@momjian.us, nagata@sraoss.co.jp, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
In-Reply-To: <3190751.1657845414@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox