From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Prepare to support non-tables in publications |
Date: | 2020-03-19 08:04:42 |
Message-ID: | E1jEqAU-0005vJ-Rj@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Prepare to support non-tables in publications
This by itself doesn't change any functionality but prepares the way
for having relations other than base tables in publications.
Make arrangements for COPY handling the initial table sync. For
non-tables we have to use COPY (SELECT ...) instead of directly
copying from the table, but then we have to take care to omit
generated columns from the column list.
Also, remove a hardcoded reference to relkind = 'r' and rely on the
publisher to send only what it can actually publish, which will be
correct even in future cross-version scenarios.
Reviewed-by: Amit Langote <amitlangote09(at)gmail(dot)com>
Discussion: https://www.postgresql.org/message-id/flat/CA+HiwqH=Y85vRK3mOdjEkqFK+E=ST=eQiHdpj43L=_eJMOOznQ(at)mail(dot)gmail(dot)com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/c314c147c0563c9758bdad988ffda8d64daa2db6
Modified Files
--------------
src/backend/replication/logical/tablesync.c | 36 +++++++++++++++++++++--------
src/include/replication/logicalproto.h | 1 +
2 files changed, 28 insertions(+), 9 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2020-03-19 08:10:17 | pgsql: Make pg_basebackup ask the server to estimate the total backup s |
Previous Message | Fujii Masao | 2020-03-19 06:33:28 | pgsql: Rename the recovery-related wait events. |