| From: | Vadim Lakt <vadim(dot)lakt(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: long-standing data loss bug in initial sync of logical replication |
| Date: | 2024-01-16 10:24:02 |
| Message-ID: | de81e05f-17a5-478e-bd7b-dcd4e28c3dff@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 19.11.2023 09:18, Andres Freund wrote:
> Yea, the situation is much simpler during logical decoding than "originally" -
> there's no concurrency.
>
> Greetings,
>
> Andres Freund
>
We've encountered a similar error on our industrial server.
The case: After adding a table to logical replication, table
initialization proceeds normally, but new data from the publisher's
table does not appear on the subscriber server. After we added the
table, we checked and saw that the data was present on the subscriber
and everything was normal, we discovered the error after some time. I
have attached scripts to the email.
The patch from the first message also solves this problem.
--
Best regards,
Vadim Lakt
| Attachment | Content-Type | Size |
|---|---|---|
| err_logical_replication.zip | application/zip | 2.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2024-01-16 10:30:14 | sql-merge.html Compatibility section, typo. |
| Previous Message | Amit Langote | 2024-01-16 10:00:29 | Re: remaining sql/json patches |