Mostly to close the loop on this, now that I have things going seemingly
reliably...
On Tue, 18 Jun 2024 at 14:33, Ron Johnson wrote:
> On Tue, Jun 18, 2024 at 5:03 AM Shaheed Haque
> wrote:
>
>> Hi all,
>>
>> Is there an "official" pairing of LSN values on the publication and
>> subscription s
On Tue, Jun 18, 2024 at 5:03 AM Shaheed Haque
wrote:
> Hi all,
>
> Is there an "official" pairing of LSN values on the publication and
> subscription sides that should be used to track the delta between the two
> systems? I ask because Google is full of different pairs being used. I
> tried to id
Hi all,
Is there an "official" pairing of LSN values on the publication and
subscription sides that should be used to track the delta between the two
systems? I ask because Google is full of different pairs being used. I
tried to identify the highest level interface points exposed, i.e. what is
do
This is great, thank you for posting. I'm currently a subcontinent or two
away from my dev env, but will compare your approach with mine (you are
using some facilities of psql I'm not familiar with). At least you have
confirmed that LSNs are the place to start.
Thanks again, Shaheed
On Tue, 30 J
Hi Saheed!
I monitor our replication this way:
1. Every 10 seconds i fetch the current LSN and write it into a table,
next with the current timestamp. Further I fetch confirmend LSNs from
the replication slots and delete old entries in lsn2data table.
calculate_logical_replication_lag.php:
Hi,
I've been playing with logical replication (currently on PG14),
specifically in an AWS RDS Postgres context, but NOT using AWS' own
replication tooling. I'm generally familiar with the challenges of
distributed systems (such causality, time synchronisation etc), but not
especially familiar wit
