From: | Michael Lewis <mlewis(at)entrata(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Temp tables and replication identities |
Date: | 2019-02-12 18:30:58 |
Message-ID: | CAHOFxGpnP3Pf5bWRhyP-3NxgtfJsTNMzo0YtvNC75iB+4a=eTw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I am curious about receiving an error on updating/inserting into a temp
table when a replication for "all tables' is created in PG 10.6. Given temp
tables are not replicated, it seems odd that an update fails unless a
replication identity is defined.
To reproduce, try the below code. Uncomment line 3 and the error is gone of
course. It just seems like the identity should not be need to be defined on
a temp table since it won't be replicated anyway.
CREATE publication test1 FOR ALL TABLES;
CREATE TEMP TABLE testing123 ON COMMIT DROP AS ( SELECT 1 AS value );
/* ALTER TABLE pg_temp.testing123 REPLICA IDENTITY FULL; */
UPDATE testing123 SET value = 2;
*Michael Lewis | Software Engineer*
*Entrata*
*c: **619.370.8697 <619-370-8697>*
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Lewis | 2019-02-12 18:33:20 | Re: Postgresql RDS DB Latency Chossing Hash join Plan |
Previous Message | github kran | 2019-02-12 18:27:23 | Postgresql RDS DB Latency Chossing Hash join Plan |