Re: Logical replication is missing block of rows when sending initial sync?

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, kuroda(dot)hayato(at)fujitsu(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Logical replication is missing block of rows when sending initial sync?
Date: 2023-11-03 12:22:42
Message-ID: ZUTmEi8mEoDl93Vm@depesz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Nov 03, 2023 at 01:20:22PM +0100, Tomas Vondra wrote:
> I think it'd be interesting to know:
>
> 1) Commit LSN for the missing rows (for the xmin).
>
> 2) Are the other changes for these transactions that *got* replicated
> correctly?

How would I know?

> 3) LSNs used for the tablesync slot, catchup etc. I believe those are in
> the server log.

I will provide more logs on the next problem.

Best regards,

depesz

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Koray Yavuz 2023-11-03 13:27:58 Re: BUG #18181: KB5031455 Update crashes PostgreSQL Server for Turkish language
Previous Message Tomas Vondra 2023-11-03 12:20:22 Re: Logical replication is missing block of rows when sending initial sync?