Re: BUG #18203: Logical Replication initial sync failure - Mailing list pgsql-bugs

From vignesh C
Subject Re: BUG #18203: Logical Replication initial sync failure
Date
Msg-id CALDaNm2kSJCVree6R1iKxjbA=Sg4raFi3Fi_+wfF2xn2roxqCg@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18203: Logical Replication initial sync failure  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: BUG #18203: Logical Replication initial sync failure  (Peter Smith <smithpb2250@gmail.com>)
List pgsql-bugs
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

Attachment

pgsql-bugs by date:

Previous
From: Peter Smith
Date:
Subject: Re: BUG #18203: Logical Replication initial sync failure
Next
From: vignesh C
Date:
Subject: Re: BUG #18203: Logical Replication initial sync failure