Re: Add option --drop-cascade for pg_dump/restore - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: Add option --drop-cascade for pg_dump/restore
Date
Msg-id CAKAnmmLCOnXA4H=LJdG-hje3iQHyAW4_jp0kpYrV_SkVQVDTZw@mail.gmail.com
Whole thread Raw
In response to Re: Add option --drop-cascade for pg_dump/restore  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Add option --drop-cascade for pg_dump/restore  (Wu Haotian <whtsky@gmail.com>)
List pgsql-hackers
On Fri, Jul 16, 2021 at 9:40 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
That would require pg_restore to try to edit the DROP commands during
restore, which sounds horribly fragile.  I'm inclined to think that
supporting this option only during initial dump is safer.

Safer, but not nearly as useful. Maybe see what the OP (Wu Haotian) can come up with as a first implementation? 

Cheers,
Greg

pgsql-hackers by date:

Previous
From: Greg Sabino Mullane
Date:
Subject: Re: Avoid stuck of pbgench due to skipped transactions
Next
From: Andrew Dunstan
Date:
Subject: Re: Postgres perl module namespace