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

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, Wu Haotian <whtsky(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-08-10 14:57:19
Message-ID: CAKAnmmLCOnXA4H=LJdG-hje3iQHyAW4_jp0kpYrV_SkVQVDTZw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jul 16, 2021 at 9:40 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2021-08-10 15:02:13 Re: Postgres perl module namespace
Previous Message Greg Sabino Mullane 2021-08-10 14:50:20 Re: Avoid stuck of pbgench due to skipped transactions