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 21:06:45 |
Message-ID: | b3d337ae-00bc-ee49-0466-d471b27f4b2f@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 5/25/17 09:55, Robert Haas wrote:
> On Thu, May 25, 2017 at 8:32 AM, Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>>> 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.
>
> Sure, that case is hard to address. But why is *this* case hard to address?
They are the same cases.
a) Create object in information_schema.
b) Create another object elsewhere that depends on it.
c) pg_dump will dump (b) but not (a).
So the fix, if any, would be to prevent (a), or prevent (b), or fix (c).
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-05-25 21:08:57 | Re: No parameter values checking while creating Alter subscription...Connection |
Previous Message | Regina Obe | 2017-05-25 20:47:30 | PostgreSQL 10 changes in exclusion constraints - did something change? |