Re: BUG #18203: Logical Replication initial sync failure
vignesh C <vignesh21@gmail.com>
From: vignesh C <vignesh21@gmail.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: zzzzz.graf@gmail.com, pgsql-bugs@lists.postgresql.org
Date: 2023-11-21T05:28:05Z
Lists: pgsql-bugs
Attachments
- v2-0001-Specify-parenthesis-for-tablesync-worker-copy-com.patch (text/x-patch) patch v2-0001
- v2-0001-Specify-parenthesis-for-tablesync-worker-copy-com_PG15.patch (text/x-patch) patch v2-0001
On Mon, 20 Nov 2023 at 18:38, Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Mon, Nov 20, 2023 at 2:53 PM vignesh C <vignesh21@gmail.com> wrote: > > > > > > > > Logical replication worker returns with the following error: > > > 2023-11-17 20:40:16.141 UTC [151084] ERROR: could not start initial > > > contents copy for table "public.no_col": ERROR: syntax error at or near > > > ")" > > > LINE 1: COPY public.no_col () TO STDOUT > > > > Thanks for reporting this issue, I was able to reproduce the issue. > > This issue is happening because we are trying to specify the column > > list while the table sync worker is copying data for the table. > > I felt we should not specify the column list when the table has no columns. > > Attached patch has the changes to handle the same. > > > > I think we can add a test for such cases which tests both initial sync > and regular replication on a table with no column. I have added a test for the same and tested upto PG15 where the changes were added. The patches for the same are attached. Regards, Vignesh
Commits
-
Fix the initial sync tables with no columns.
- eeb0ebad79d9 17.0 landed
- 1b6da28e0668 16.2 landed
- 57aae65aee26 15.6 landed