Re: Physical replication slot advance is not persistent

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alexey Kondratov <a(dot)kondratov(at)postgrespro(dot)ru>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, andres(at)anarazel(dot)de, dim(at)tapoueh(dot)org, pgsql-hackers(at)postgresql(dot)org, simon(at)2ndquadrant(dot)com
Subject: Re: Physical replication slot advance is not persistent
Date: 2020-06-18 07:47:46
Message-ID: 20200618074746.GG118592@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 16, 2020 at 04:27:27PM +0900, Michael Paquier wrote:
> We could do that. Now I found cleaner the direct comparison of
> pg_replication_slots.restart before and after the restart. So I have
> kept it.

And done. There were conflicts in 001_stream_rep.pl for 11 and 12 but
I have reworked the patch on those branches to have a minimum amount
of diffs with the other branches. This part additionally needed to
stop standby_1 before running the last part of the test to be able to
drop its physical slot on the primary.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2020-06-18 09:55:10 Re: [Patch] ALTER SYSTEM READ ONLY
Previous Message Juan José Santamaría Flecha 2020-06-18 07:43:54 Re: factorial of negative numbers