Re: pg_dump ignoring information_schema tables which used in Create Publication.

On Fri, May 26, 2017 at 10:46:12PM -0300, Euler Taveira wrote:
> 2017-05-26 17:52 GMT-03:00 Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>:
> > You cannot publish a system catalog. But a user-created table in
> > information_schema is not a system catalog.
>
> Replication of information_schema tables works. However, pg_dump doesn't
> include information_schema tables into CREATE PUBLICATION command
> (user-defined information_schema tables aren't included in pg_dump even
> *before* logical replication). IMO allow publish/subscribe of tables into
> information_schema is harmless (they aren't special tables like catalogs).
> Also, how many people would create real tables into information_schema?
> Almost zero. Let's leave it alone. Since pg_dump doesn't document that
> information_schema isn't dumped, I think we shouldn't document this for
> logical replication.

[Action required within three days. This is a generic notification.]

The above-described topic is currently a PostgreSQL 10 open item. Peter,
since you committed the patch believed to have created it, you own this open
item. If some other commit is more relevant or if this does not belong as a
v10 open item, please let us know. Otherwise, please observe the policy on
open item ownership[1] and send a status update within three calendar days of
this message. Include a date for your subsequent status update. Testers may
discover new open items at any time, and I want to plan to get them all fixed
well in advance of shipping v10. Consequently, I will appreciate your efforts
toward speedy resolution. Thanks.

[1] https://www.postgresql.org/message-id/20170404140717.GA2675809%40tornado.leadboat.com