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

From: Wu Haotian <whtsky(at)gmail(dot)com>
To: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
Cc: vignesh C <vignesh21(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add option --drop-cascade for pg_dump/restore
Date: 2021-08-16 06:35:06
Message-ID: CADHB_-C6mfjQtwy3Lno4Ua5qgHwDH2Ad9K9s7R7Y+JKsxKLWNA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

There are already documents for "--clean only works with plain text output",
so adding checks for --clean seems like a breaking change to me.

I've updated the docs to indicate --drop-cascade and --if-exists only
works with plain text output.

Attachment Content-Type Size
0004-pg_dump-restore-add-drop-cascade-option.patch application/octet-stream 21.2 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2021-08-16 06:43:51 Re: logical replication empty transactions
Previous Message Michael Paquier 2021-08-16 06:27:26 Re: ECPG bug fix: DECALRE STATEMENT and DEALLOCATE, DESCRIBE