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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_replication_slot_advance to return NULL instead of 0/0 if slot not advanced
Date: 2018-06-11 00:30:28
Message-ID: 20180611003028.GA7066@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-06-11 00:37:56 Re: Possible bug in logical replication.
Previous Message Tom Lane 2018-06-11 00:19:46 Re: Internal error XX000 with enable_partition_pruning=on, pg 11 beta1 on Debian