Re: Creation of temporary tables on a publisher

From: Shreeyansh Dba <shreeyansh2014(at)gmail(dot)com>
To: Cory Nemelka <cnemelka(at)gmail(dot)com>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Creation of temporary tables on a publisher
Date: 2019-01-24 01:56:14
Message-ID: CAGDYbUOz3ZqqUon6gkj4d5WsY-3Lj0_jD91AGQQZPQBuTS14zw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-sql

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(at)gmail(dot)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
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Nagy László Zsolt 2019-01-24 06:35:17 constraint deferred but fails?
Previous Message Cory Nemelka 2019-01-23 22:45:39 Creation of temporary tables on a publisher

Browse pgsql-sql by date

  From Date Subject
Next Message Cory Nemelka 2019-01-24 16:34:02 Re: Creation of temporary tables on a publisher
Previous Message Cory Nemelka 2019-01-23 22:45:39 Creation of temporary tables on a publisher