Postgres Pro
Downloads
Home   >   mailing lists

Re: replication slot restart_lsn initialization - Mailing list pgsql-hackers

From Andres Freund
Subject Re: replication slot restart_lsn initialization
Date
Msg-id 20150610153604.GG10551@awork2.anarazel.de
Whole thread Raw
In response to Re: replication slot restart_lsn initialization  (Gurjeet Singh <gurjeet@singh.im>)
Responses Re: replication slot restart_lsn initialization  (Gurjeet Singh <gurjeet@singh.im>)
List pgsql-hackers
Tree view 
On 2015-06-10 08:24:23 -0700, Gurjeet Singh wrote:
> On Wed, Jun 10, 2015 at 8:07 AM, Andres Freund <andres@anarazel.de> wrote:
> > That doesn't look right to me. Why is this code logging a standby
> > snapshot for physical slots?
> >
> 
> This is the new function I referred to above. The logging of the snapshot
> is in 'not RecoveryInProgress()' case, meaning it's running in primary and
> not in a standby.

It's still done uselessly for physical slots?

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: s_lock() seems too aggressive for machines with many sockets
Next
From: Andres Freund
Date:
Subject: Re: s_lock() seems too aggressive for machines with many sockets