From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Ian Lawrence Barwick <barwick(at)gmail(dot)com> |
Cc: | 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:48:45 |
Message-ID: | CABUevEziaz9yZaCgMmLHpzVb1+vGC7zjkFdJnYwYEZH6UkFGZQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 6, 2020 at 3:45 PM Ian Lawrence Barwick <barwick(at)gmail(dot)com>
wrote:
> 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.
>
Argh, perfect timing. I'll update with your new version :)
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2020-10-06 13:52:11 | Re: Transactions involving multiple postgres foreign servers, take 2 |
Previous Message | Magnus Hagander | 2020-10-06 13:48:05 | Re: [doc] clarify behaviour of pg_dump's -t/--table option with non-tables |