Re: Creation of temporary tables on a publisher - Mailing list pgsql-admin

From Shreeyansh Dba
Subject Re: Creation of temporary tables on a publisher
Date
Msg-id CAGDYbUOz3ZqqUon6gkj4d5WsY-3Lj0_jD91AGQQZPQBuTS14zw@mail.gmail.com
Whole thread Raw
In response to Creation of temporary tables on a publisher  (Cory Nemelka <cnemelka@gmail.com>)
Responses Re: Creation of temporary tables on a publisher  (Cory Nemelka <cnemelka@gmail.com>)
List pgsql-admin
In Logical replication all tables have a valid default REPLICA IDENTITY (i.e. PK). If suppose there isn't one then You could try to set identity to full, with will use whole row as identifier ALTER TABLE name REPLICA IDENTITY FULL;

or if it has unique index ALTER TABLE name USING INDEX index_name;

Thanks & Regards,
Shreeyansh DBA Team
www.shreeyansh.com


On Thu, Jan 24, 2019 at 4:16 AM Cory Nemelka <cnemelka@gmail.com> wrote:
Postgresql v10.6

After defining a publication with "FOR ALL TABLES" clause, temporary tables that are created after the definition will produce errors if they are updated,etc.  The error: "cannot update table <tablename> because it does not have a replica identity and publishes updates."

Is this expected behaviour?  I had understood that temporary tables were not included in publications.


--cnemelka

pgsql-admin by date:

Previous
From: Cory Nemelka
Date:
Subject: Creation of temporary tables on a publisher
Next
From: Nagy László Zsolt
Date:
Subject: constraint deferred but fails?