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-10T13:19:23Z
Lists: pgsql-hackers 
On Wed, Jun 06, 2018 at 11:04:39AM +0900, Michael Paquier wrote:
> I am attaching as well the patch I sent yesterday.  0001 is candidate
> for a back-patch, 0002 is for HEAD to fix the slot advance stuff.

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.
--
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