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

From: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
To: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, "'depesz(at)depesz(dot)com'" <depesz(at)depesz(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Logical replication is missing block of rows when sending initial sync?
Date: 2023-11-17 14:40:35
Message-ID: dd5c48d4-8962-d1c9-e71a-6bda23b86401@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 11/15/23 02:41, Hayato Kuroda (Fujitsu) wrote:
> Dear Tomas, Depesz,
>
>>
>>> I'll try reproducing this locally over the weekend. Should I use the
>>> test_1030.sh script that you shared a week ago, or do I need to do
>>> something more?
>>
>> That question is probably not to me, but to Hayato Kuroda
>
> Just FYI - As I posted, this script could not reproduce the issue. We may use the same table definition
> but I have not tried yet. I will let you know if I succeeded to reproduce.
>

FYI I think I've reproduced the issue (with a different script), I've
started a thread on pgsql-hackers:

https://www.postgresql.org/message-id/de52b282-1166-1180-45a2-8d8917ca74c6%40enterprisedb.com

Obviously, I can't be sure it's exactly the same issue, but the symptoms
seem to match what Depesz reported (gaps in data etc.). I don't know
what the root cause is, or fix. But there's more info (and scripts) in
the hackers thread.

regards

--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2023-11-17 15:17:23 Re: BUG #18202: pg_constraint data isn't refreshed when using alter rename to on a constraint trigger
Previous Message PG Bug reporting form 2023-11-17 14:31:35 BUG #18202: pg_constraint data isn't refreshed when using alter rename to on a constraint trigger