| From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org, Ron <ronljohnsonjr(at)gmail(dot)com> |
| Subject: | Re: Drop role cascade ? |
| Date: | 2022-11-18 05:34:06 |
| Message-ID: | 95EF7001-C69F-430A-8E0E-3464A1A8414B@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 18 November 2022 01:14:37 CET, Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
>On 11/17/22 17:57, Tom Lane wrote:
>> Ron <ronljohnsonjr(at)gmail(dot)com> writes:
>>> On 11/17/22 17:16, Tom Lane wrote:
>>>> Not directly, but see REASSIGN OWNED and DROP OWNED.
>>> SIMULATE and VERBOSE options would be handy, to see what those commands
>>> would actually do.
>> Hmph. I'm surprised to realize that those commands don't produce
>> trace output comparable to DROP CASCADE. If they did, this need
>> would be met by the traditional hack of "BEGIN; DROP ...; ROLLBACK".
>
>So... you'll add it to v16???? :D
>
+1 as feature request
--
Andreas Kretschmer, EDB
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2022-11-18 06:13:24 | Re: Drop role cascade ? |
| Previous Message | gzh | 2022-11-18 03:25:07 | Re: An I/O error occured while sending to the backend |