Horton

Re: pg_replication_slot_advance to return NULL instead of 0/0 if slot not advanced

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Petr Jelinek <petr.jelinek@2ndquadrant.com>
Cc: Simon Riggs <simon@2ndquadrant.com>, Magnus Hagander <magnus@hagander.net>, Postgres hackers <pgsql-hackers@postgresql.org>
Date: 2018-06-11T00:30:28Z
Lists: pgsql-hackers 
On Sun, Jun 10, 2018 at 10:19:23PM +0900, Michael Paquier wrote:
> I have been able to look again at 0001 and pushed it as 9e149c8.  As
> reading inconsistent data from replication slots is rather hard to
> trigger, I have just pushed the patch to HEAD.  I'll look at 0002
> tomorrow.

And pushed 0002 as f731cfa9, so we should be good with this open item.
--
Michael

Commits

  1. Fix a couple of bugs with replication slot advancing feature

  2. Fix and document lock handling for in-memory replication slot data