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-25 12:32:58 |
Message-ID: | c0633d95-8996-1c2d-1c57-e2ff484c932f@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 5/24/17 21:36, Robert Haas wrote:
> On Wed, May 24, 2017 at 7:16 PM, Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>> On 5/22/17 07:42, Kuntal Ghosh wrote:
>>> pg_dump ignores anything created under object name "pg_*" or
>>> "information_schema".
>>
>> Publications have a slightly different definition of what tables to
>> ignore/prohibit than pg_dump, partly because they have more built-in
>> knowledge. I'm not sure whether it's worth fixing this.
>
> Well, I think if it's not going to work, it should be prohibited,
> rather than seeming to work but then not actually working.
Here is a similar case that pg_dump fails on:
create table information_schema.test1 (a int);
create view public.test2 as select * from information_schema.test1;
It's not clear how to address that, or whether it's worth it.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2017-05-25 12:51:55 | Re: Server ignores contents of SASLInitialResponse |
Previous Message | Sokolov Yura | 2017-05-25 12:22:03 | Fix performance of generic atomics |