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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: nagata(at)sraoss(dot)co(dot)jp, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17434: CREATE/DROP DATABASE can be executed in the same transaction with other commands
Date: 2022-07-15 00:36:54
Message-ID: 3190751.1657845414@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2022-07-15 00:48:57 Re: [15] Custom WAL resource managers, single user mode, and recovery
Previous Message Jeff Davis 2022-07-15 00:22:54 [15] Custom WAL resource managers, single user mode, and recovery

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2022-07-15 00:49:36 Re: Doc about how to set max_wal_senders when setting minimal wal_level
Previous Message Bruce Momjian 2022-07-15 00:01:41 Re: Fix typo in progress reporting doc