| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Kouber Saparev <kouber(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org, wangsh(dot)fnst(at)fujitsu(dot)com, osumi(dot)takamichi(at)fujitsu(dot)com, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Subject: | Re: Logical replication breaks: "unexpected duplicate for tablespace 0, relfilenode 2774069304" |
| Date: | 2023-12-24 01:36:56 |
| Message-ID: | ZYeLOF18fcS2x0Cb@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Dec 22, 2023 at 10:55:24AM +0200, Kouber Saparev wrote:
> The table for this file node is not even included in any of the
> publications we have. I've found a similar issue described [1] before, so I
> was wondering whether this patch is applied? Our subscriber database is
> PostgreSQL 16.1 and the publisher - PostgreSQL 15.4.
Or just this link using the community archives based on the
message-ID:
https://www.postgresql.org/message-id/TYCPR01MB83731ADE7FD7C7CF5D335BCEEDE99@TYCPR01MB8373.jpnprd01.prod.outlook.com
> What quick solution would fix the replication? Repack of the table? Reload
> of the database? Killing some backends?
There may be something you could do as a short-term solution, but it
does not solve the actual root of the problem, because the error you
are seeing is not something users should be able to face.
The first problem that we have here is that we've lost track of the
patch proposed, so I have added a CF entry for now:
https://commitfest.postgresql.org/46/4720/
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-12-24 15:43:35 | Re: Version 16.x search_path behavior change? |
| Previous Message | Adrian Klaver | 2023-12-23 22:35:04 | Re: Unable to start postgresql-14 |