Re: Add option --drop-cascade for pg_dump/restore

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Wu Haotian <whtsky(at)gmail(dot)com>
Cc: daniel(at)yesql(dot)se, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add option --drop-cascade for pg_dump/restore
Date: 2021-11-03 19:03:55
Message-ID: 142976.1635966235@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Wu Haotian <whtsky(at)gmail(dot)com> writes:
> here's the rebased patch.

Looks like it needs rebasing again, probably as a result of our recent
renaming of our Perl test modules.

FWIW, I'd strongly recommend that it's time to pull all that SQL code
hacking out of RestoreArchive and put it in its own function.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-11-03 19:07:47 Re: pg14 psql broke \d datname.nspname.relname
Previous Message Stephen Frost 2021-11-03 18:46:07 Re: Predefined role pg_maintenance for VACUUM, ANALYZE, CHECKPOINT.