From: | Ian Lawrence Barwick <barwick(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [doc] clarify behaviour of pg_dump's -t/--table option with non-tables |
Date: | 2020-10-06 13:44:59 |
Message-ID: | CAB8KJ=hijOtVKuRz6fY573RrUK5yPOO3r99n+c9DARuCKHb+Qw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2020年10月6日(火) 21:58 Ian Lawrence Barwick <barwick(at)gmail(dot)com>:
>
> Hi
>
> Recently I ran into a case where someone was wondering why it was not
> possible to dump the contents of a view, even though the documentation [1]
> seems to imply this is possible.
>
> Currently it says:
>
> Dump only tables with names matching pattern. For this purpose, "table"
> includes views, materialized views, sequences, and foreign tables.
>
> The attached patch attempts to clarify that only definitions of those objects
> will be dumped, and also mentions that dumping foreign table data requires the
> --include-foreign-data option.
>
> I suggest backpatching any changes to Pg13 where the --include-foreign-data
> option was added.
>
> [1] https://www.postgresql.org/docs/current/app-pgdump.html
Better version attached.
Regards
Ian Barwick
--
EnterpriseDB: https://www.enterprisedb.com
Attachment | Content-Type | Size |
---|---|---|
doc-pg_dump-clarify-table-option.v2.patch | text/x-patch | 2.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2020-10-06 13:48:05 | Re: [doc] clarify behaviour of pg_dump's -t/--table option with non-tables |
Previous Message | Bharath Rupireddy | 2020-10-06 13:40:02 | Re: Parallel INSERT (INTO ... SELECT ...) |