| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump --exclude-* options documentation |
| Date: | 2019-09-03 12:28:17 |
| Message-ID: | e0799beb-c6ca-d6c1-c8e7-37a9ae99f2ef@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-09-02 16:55, Tom Lane wrote:
> 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.
done
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2019-09-03 12:44:25 | Re: [PATCH] Speedup truncates of relation forks |
| Previous Message | Fabien COELHO | 2019-09-03 11:55:15 | Re: pgbench - rework variable management |