Re: Synchronizing slots from primary to standby - Mailing list pgsql-hackers

From SATYANARAYANA NARLAPURAM
Subject Re: Synchronizing slots from primary to standby
Date
Msg-id CAHg+QDej2qZizH98o+pBNQZNsCyO+q9BScFvS42X1OX92M6+8Q@mail.gmail.com
Whole thread Raw
In response to Re: Synchronizing slots from primary to standby  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: Synchronizing slots from primary to standby
List pgsql-hackers

3) Instead of the subscriber pulling the slot info, why can't the
publisher (via the walsender or a new bg worker maybe?) push the
latest slot info? I'm not sure we want to add more functionality to
the walsender, if yes, isn't it going to be much simpler?

Standby pulling the information or at least making a first attempt to connect to the  primary is a better design as primary doesn't need to spend its cycles repeatedly connecting to an unreachable standby. In fact, primary wouldn't even need to know the followers, for example followers / log shipping standbys

pgsql-hackers by date:

Previous
From: SATYANARAYANA NARLAPURAM
Date:
Subject: Switching XLog source from archive to streaming when primary available
Next
From: Laurenz Albe
Date:
Subject: Re: Contributing