| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | koderan(at)yandex(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18415: Logical replication errors. |
| Date: | 2024-03-28 17:02:41 |
| Message-ID: | CAKFQuwYLbPXtSWe0XpqO7u_rzbzgqVzQ4DHLo6uVYPTr2ottXw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Mar 28, 2024 at 9:59 AM PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18415
> Logged by: Andy Kosheen
> Email address: koderan(at)yandex(dot)ru
> PostgreSQL version: 15.4
> Operating system: Oracle Linux Server 8.4
> Description:
>
> In the process of logical replication from version 13.3 (on Ubuntu 16.04.6
> LTS) to version 15.4 (on Oracle Linux Server 8.4), when most of the data
> has
> already been transferred, the following errors begin to occur, appearing
> endlessly until you stop the replication process (this situation occurs on
> databases larger than at least 50GB, even if there is a small number of
> transactions on the source database):
> 2024-03-20 03:19:41.410 +07 [3433858] LOG: logical replication apply
> worker
> for subscription "log_rep_sub" has started
> 2024-03-20 03:19:41.425 +07 [3433858] ERROR: could not start WAL
> streaming:
> ERROR: replication slot "log_rep_sub" does not exist
>
>
Suggest you check the publisher logs and see why the replication slot went
away.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | koderan | 2024-03-28 19:40:54 | Re: BUG #18415: Logical replication errors. |
| Previous Message | PG Bug reporting form | 2024-03-28 16:16:23 | BUG #18415: Logical replication errors. |