On Fri, Jul 23, 2021 at 10:56 AM tanghy.fnst@fujitsu.com
<tanghy.fnst@fujitsu.com> wrote:
>
>
> After applying your V13 patch. I noticed that if I specify duplicate schema names when using "ALTER PUBLICATION ...
SETSCHEMA ...", I would get the following error message:
>
> postgres=# ALTER PUBLICATION pub1 SET SCHEMA s1,s1;
> ERROR: duplicate key value violates unique constraint "pg_publication_sch_psnspcid_pspubid_index"
> DETAIL: Key (psnspcid, pspubid)=(16406, 16405) already exists.
>
That definitely seems to be a bug, since "ALTER PUBLICATION ... SET
TABLE ..." ignores duplicates and there is no ERROR.
"CREATE PUBLICATION ... SET SCHEMA s1, s1;" and "ALTER PUBLICATION ...
ADD SCHEMA s1, s1;" also give the same kind of error.
Regards,
Greg Nancarrow
Fujitsu Australia
