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-10 13:19:23
Message-ID: 20180610131923.GA15065@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2018-06-10 14:41:26 CF bug fix items
Previous Message David Rowley 2018-06-10 13:16:23 Re: Internal error XX000 with enable_partition_pruning=on, pg 11 beta1 on Debian