Re: Physical replication slot advance is not persistent
Alexey Kondratov <a.kondratov@postgrespro.ru>
From: Alexey Kondratov <a.kondratov@postgrespro.ru>
To: Michael Paquier <michael@paquier.xyz>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, craig@2ndquadrant.com,
andres@anarazel.de, pgsql-hackers@postgresql.org, simon@2ndquadrant.com
Date: 2020-01-31T11:14:03Z
Lists: pgsql-hackers
On 30.01.2020 05:19, Michael Paquier wrote: > On Wed, Jan 29, 2020 at 05:10:20PM +0900, Kyotaro Horiguchi wrote: >> Looks perfect. > Thanks Horiguchi-san and others. Applied and back-patched down to > 11. Great! Thanks for getting this done. -- Alexey Kondratov Postgres Professional https://www.postgrespro.com Russian Postgres Company
Commits
-
Fix oldest xmin and LSN computation across repslots after advancing
- 1657e14b50d2 11.9 landed
- 16f43122d46f 12.4 landed
- 43e70addf5a6 13.0 landed
- b48df818dcbd 14.0 landed
-
Fix slot data persistency when advancing physical replication slots
- 374464c3e96f 11.7 landed
- 3228512b7b2b 12.2 landed
- b0afdcad21fd 13.0 landed