Re: pg_dump --exclude-* options documentation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump --exclude-* options documentation
Date: 2019-09-02 14:55:01
Message-ID: 25411.1567436101@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> writes:
>> Should we change the documentation of the old pg_dump options to also
>> take a "pattern", or change the documentation of the new pg_dumpall
>> option to read "database"?

> My 0.02€: we should use the more general and precise, i.e. pattern.

+1 ... it doesn't seem to me that "--exclude-schema=schema" conveys
anything useful.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kohei KaiGai 2019-09-02 14:58:08 Re: add a MAC check for TRUNCATE
Previous Message Chapman Flack 2019-09-02 14:52:29 Re: safe to overload objectSubId for a type?