Re: [HACKERS] Subscription code improvements - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Subscription code improvements
Date
Msg-id a41d2469-c46f-e574-b2ff-7feb943dc8bd@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Subscription code improvements  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: [HACKERS] Subscription code improvements  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On 8/7/17 00:27, Masahiko Sawada wrote:
>>> However, even with this patch there is still an issue that NOTICE
>>> messages "removed subscription for table public.t1" can be appeared
>>> even if we rollback ALTER SUBSCRIPTION REFRESH command as I mentioned
>>> on earlier thread. Since I think this behaviour will confuse users who
>>> check server logs I'd like to deal with it, I don't have a good idea
>>> though.
>>
>> Maybe we can just remove those messages?
>>
>> We don't get messages when we create a subscription about which tables
>> are part of it.  So why do we need such messages when we refresh a
>> subscription?
> 
> I think that the messages is useful when we add/remove tables to/from
> the publication and then refresh the subscription, so we might want to
> change it to DEBUG rather than elimination.

Good idea.  Done that way.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Subscription code improvements
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Adding hook in BufferSync for backup purposes