From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ron Johnson <ronljohnsonjr@gmail.com>
cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: REVOKE ALL ON ALL OBJECTS IN ALL SCHEMAS FROM some_role?
In-reply-to: 
 <CANzqJaDuyYD2Pqzng_MqEM2BN02wcQOKqz2ntV0GFs4sV2RVyA@mail.gmail.com>
References: 
 <CANzqJaDu+7q9i=-vwUsX-ZZRTKSCCCG7FVF32X7XhPo1E4Xpxg@mail.gmail.com>
 <D1C4B519-67B6-446A-92DF-A33D095FD215@elevated-dev.com>
 <bacddcb84956a662cd3de97ce4fe32d705083dc7.camel@cybertec.at>
 <CANzqJaDuyYD2Pqzng_MqEM2BN02wcQOKqz2ntV0GFs4sV2RVyA@mail.gmail.com>
Comments: In-reply-to Ron Johnson <ronljohnsonjr@gmail.com>
	message dated "Tue, 08 Jul 2025 08:59:50 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <687004.1751980677.1@sss.pgh.pa.us>
Date: Tue, 08 Jul 2025 09:17:57 -0400
Message-ID: <687005.1751980677@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/687005.1751980677%40sss.pgh.pa.us>
Precedence: bulk

Ron Johnson <ronljohnsonjr@gmail.com> writes:
> Cascading statements really need a DRY RUN option.

[ shrug ] BEGIN/ROLLBACK serves that purpose fine, in fact better
than a per-statement "dry run" option would do: you can run several
dependent DDL statements and then look around at the results before
committing (or not).

Your claim that rollback is slow seems to be born of experience with
some other DBMS.

			regards, tom lane