This part. If you can read perl :), https://github.com/postgres/postgres/tree/master/src/test/subscription/t
On Mon, May 31, 2021, 9:02 PM Willy-Bas Loos <willy...@gmail.com> wrote: > > > On Mon, May 31, 2021 at 4:24 PM Vijaykumar Jain < > vijaykumarjain.git...@gmail.com> wrote: > >> So I got it all wrong it seems :) >> > Thank you for taking the time to help me! > > You upgraded to pg13 fine? , but while on pg13 you have issues with >> logical replication ? >> > Yes, the upgrade went fine. So here are some details: > I already had londiste running on postgres 9.3, but londiste wouldn't run > on Debian 10 > So i first made the new server Debian 9 with postgres 9.6 and i started > replicating with londiste from 9.3 to 9.6 > When all was ready, i stopped the replication to the 9.6 server and > deleted all londiste & pgq content with drop schema cascade. > Then I upgraded the server to Debian 10. Then i user pg_upgrade to > upgrade from postgres 9.6 to 13. (PostGIS versions were kept compatible). > Then I added logical replication and a third server as a subscriber. > > I was going to write that replication is working fine (since the table > contains a lot of data and there are no conflicts in the log), but it turns > out that it isn't. > The subscriber is behind and It looks like there hasn't been any incoming > data after the initial data synchronization. > So at least now i know that the WAL is being retained with a reason. The > connection is working properly (via psql anyway) > > I will also look into how to diagnose this from the system tables, e.g. > substracting LSN's to get some quantitative measure for the lag. > > > >> There is a path in the postgresql source user subscription folder iirc >> which covers various logical replication scenarios. >> That may help you just in case. >> > OK, so comments in the source code you mean? > >
