[prev in list] [next in list] [prev in thread] [next in thread]
List: postgresql-general
Subject: Re: WAL accumulating, Logical Replication pg 13
From: Vijaykumar Jain <vijaykumarjain.github () gmail ! com>
Date: 2021-05-31 16:12:05
Message-ID: CAM+6J97_jktD7BS6vDrPFMueSxtANeQcw6QM=CHbfLd2EWPGDQ () mail ! gmail ! com
[Download RAW message or body]
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 <willybas@gmail.com> wrote:
>
>
> On Mon, May 31, 2021 at 4:24 PM Vijaykumar Jain <
> vijaykumarjain.github@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?
>
>
[Attachment #3 (text/html)]
<div dir="auto">This part.<div dir="auto">If you can read perl :),</div><div \
dir="auto"><br><div dir="auto"><a \
href="https://github.com/postgres/postgres/tree/master/src/test/subscription/t">https: \
//github.com/postgres/postgres/tree/master/src/test/subscription/t</a></div></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 31, 2021, 9:02 PM \
Willy-Bas Loos <<a href="mailto:willybas@gmail.com">willybas@gmail.com</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div \
dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On \
Mon, May 31, 2021 at 4:24 PM Vijaykumar Jain <<a \
href="mailto:vijaykumarjain.github@gmail.com" target="_blank" \
rel="noreferrer">vijaykumarjain.github@gmail.com</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="auto">So I got it all wrong it seems \
:)</div></blockquote><div>Thank you for taking the time to help \
me!</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">You \
upgraded to pg13 fine? , but while on pg13 you have issues with logical replication ? \
</div></blockquote><div>Yes, the upgrade went fine. So here are some \
details:</div><div>I already had londiste running on postgres 9.3, but londiste \
wouldn't run on Debian 10</div><div>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</div><div>When \
all was ready, i stopped the replication to the 9.6 server and deleted all londiste \
& pgq content with drop schema cascade.</div><div>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).<br></div><div>Then I added logical replication and a \
third server as a subscriber.</div><div></div></div><div \
class="gmail_quote"><br></div><div class="gmail_quote">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.</div><div \
class="gmail_quote">The subscriber is behind and It looks like there hasn't been \
any incoming data after the initial data synchronization.</div><div \
class="gmail_quote">So at least now i know that the WAL is being retained with a \
reason. The connection is working properly (via psql anyway)<br></div><div \
class="gmail_quote"><div><br> </div><div>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.<br></div><div><br></div><div><br></div><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="auto"><br></div><div dir="auto">There is \
a path in the postgresql source user subscription folder iirc which covers various \
logical replication scenarios.</div><div dir="auto">That may help you just in \
case.</div></blockquote><div>OK, so comments in the source code you \
mean?</div></div><br></div> </blockquote></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic