| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump ignoring information_schema tables which used in Create Publication. |
| Date: | 2017-05-26 20:52:55 |
| Message-ID: | fa4b7f3f-dd59-1a9a-a4a6-b589b5dd6719@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/25/17 22:45, Robert Haas wrote:
> I guess I'm not convinced that it's really the same. I think we want
> to allow users to create views over system objects; our life might be
> easier if we hadn't permitted that, but views over e.g. pg_locks are
> common, and prohibiting them doesn't seem like a reasonable choice.
> I'm less clear that we want to let them publish system objects. Aside
> from the pg_dump issues, does it work?
The confusion in this discussion is exactly that there are multiple
definitions of what a "system object" might be.
You cannot publish a system catalog. But a user-created table in
information_schema is not a system catalog.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-05-26 20:58:55 | Re: ALTER SUBSCRIPTION ..SET PUBLICATION <no name> refresh is not throwing error. |
| Previous Message | Peter Eisentraut | 2017-05-26 20:47:13 | Re: logical replication and PANIC during shutdown checkpoint in publisher |