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

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Wu Haotian <whtsky(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-12-01 10:45:54
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> On 3 Nov 2021, at 20:03, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.

As this patch hasn't been updated, I'm marking this entry Returned with
Feedback. Please feel free to open a new entry when a rebased patch is

> 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.


Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2021-12-01 10:50:52 should we document an example to set multiple libraries in shared_preload_libraries?
Previous Message Peter Eisentraut 2021-12-01 10:32:52 Re: [PATCH] Partial foreign key updates in referential integrity triggers