Re: [HACKERS] CREATE SUBSCRIPTION log noise - Mailing list pgsql-hackers

From Petr Jelinek
Subject Re: [HACKERS] CREATE SUBSCRIPTION log noise
Date
Msg-id 6a136959-2b3a-295c-ff73-d450fe3471df@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] CREATE SUBSCRIPTION log noise  (Euler Taveira <euler@timbira.com.br>)
List pgsql-hackers
On 21/06/17 23:32, Euler Taveira wrote:
> 2017-06-21 15:14 GMT-03:00 Peter Eisentraut
> <peter.eisentraut@2ndquadrant.com
> <mailto:peter.eisentraut@2ndquadrant.com>>:
> 
>     > It doesn't appear to be contingent on anything other than the content of
>     > the command you just gave it.  I don't think we need a NOTICE saying
>     > that it did that thing I just told it to do--that should be implicit by
>     > the lack of an ERROR.
> 
>     I'm appreciative of this complaint.  The point is that we are allocating
>     resources on a remote host that should not be forgotten.  I could go
>     either way.
> 
> 
> It is documented that subscription can create a replication slot on
> remote host as mentioned in section "Replication Slot Management". If we
> want to maintain the message let's downgrade it to DEBUG1 (as we do with
> "create implicit index for table") but I prefer to rip it out.
> 

I agree with Peter here, the reason why we show this is that there is
implicit action which reserves resources on different server and is not
transactional. If we only did it when explicitly asked for, I would
agree it's not needed but given that it's default behavior I prefer to
inform the user.

--  Petr Jelinek                  http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] Get stuck when dropping a subscription duringsynchronizing table
Next
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] Logical replication: stuck spinlock atReplicationSlotRelease