From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | vignesh C <vignesh21(at)gmail(dot)com> |
Cc: | zzzzz(dot)graf(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18203: Logical Replication initial sync failure |
Date: | 2023-11-20 13:08:34 |
Message-ID: | CAA4eK1LGmEjKEH4ypOkkOs9gijVevmbKqO_RBde2HXwTxAwpkg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Nov 20, 2023 at 2:53 PM vignesh C <vignesh21(at)gmail(dot)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.
--
With Regards,
Amit Kapila.
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2023-11-20 14:04:26 | BUG #18208: ts_headline MinWords and MaxWords cannot be set to the same value |
Previous Message | Laurenz Albe | 2023-11-20 09:54:45 | Re: BUG #18196: Databases Created in Turkish Language Will Not Run on the Latest Version of Windows |