Re: [HACKERS] Re: pg_dump ignoring information_schema tables whichused in Create Publication.
От | Peter Eisentraut |
---|---|
Тема | Re: [HACKERS] Re: pg_dump ignoring information_schema tables whichused in Create Publication. |
Дата | |
Msg-id | 7910dc86-43ec-a776-f9df-dbce65eeb7f5@2ndquadrant.com обсуждение исходный текст |
Ответ на | [HACKERS] Re: pg_dump ignoring information_schema tables which used in CreatePublication. (Noah Misch <noah@leadboat.com>) |
Список | pgsql-hackers |
On 5/29/17 22:14, Noah Misch wrote: > On Fri, May 26, 2017 at 10:46:12PM -0300, Euler Taveira wrote: >> 2017-05-26 17:52 GMT-03:00 Peter Eisentraut <peter.eisentraut@2ndquadrant.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.] Unless there are any new insights, I propose to close this item as not new and not worth fixing, per the above. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: