Re: pg_dump, pg_dumpall, pg_restore: Add --no-policies option

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Nikolay Samokhvalov <nik(at)postgres(dot)ai>
Cc: pgsql-hackers mailing list <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump, pg_dumpall, pg_restore: Add --no-policies option
Date: 2025-01-10 17:44:04
Message-ID: CAKAnmmLLp6-wjFQ_U4NQ0hKxbxPRu5rLgDx1AQMwrEB0b-q11Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Looks good to me. Would ideally like to see some tests: should be easy
enough to add to t/002_pg_dump.pl, but probably not worth it just for a
simple flag like this? We don't test a lot of other flags, but on the other
hand, that's what a test suite is supposed to do.

Cheers,
Greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message James Hunter 2025-01-10 18:00:15 Proposal: "query_work_mem" GUC, to distribute working memory to the query's individual operators
Previous Message Michail Nikolaev 2025-01-10 17:06:10 Re: Why doesn't GiST VACUUM require a super-exclusive lock, like nbtree VACUUM?