From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Getting error at the time of dropping subscription and few more issues |
Date: | 2017-05-19 00:54:07 |
Message-ID: | 5456e8ff-5afd-2b04-f203-9ce0756ce2a2@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 5/12/17 13:25, Masahiko Sawada wrote:
>> postgres=# alter subscription sub set publication pub refresh;
>> NOTICE: removed subscription for table public.t1
>> NOTICE: removed subscription for table public.t2
>> ALTER SUBSCRIPTION
>>
>> I think - in publication too ,we should provide NOTICE messages.
>>
> I guess one of the reason why we emit such a NOTICE message is that
> subscriber cannot control which table the upstream server replicate.
> So if a table got disassociated on the publisher the subscriber should
> report that to user. On the other hand, since the publication can
> control it and the changes are obvious, I'm not sure we really need to
> do that.
>
> BTW I think it's better for the above NOTICE message to have subscription name.
Why? These come directly has a result of the ALTER SUBSCRIPTION
command, so you see what they refer to.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-05-19 01:00:06 | Re: [Proposal] Allow users to specify multiple tables in VACUUM commands |
Previous Message | Amit Langote | 2017-05-19 00:53:26 | Re: NOT NULL constraints on range partition key columns |