aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/cluster.c
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2018-03-21 09:13:24 -0400
committerPeter Eisentraut <peter_e@gmx.net>2018-03-21 09:15:04 -0400
commit325f2ec5557fd1c9156c910102522e04cb42d99c (patch)
treed41044a9ebc9beec2809fe61289467b107802c25 /src/backend/commands/cluster.c
parentbe8a7a6866276b228b4ffaa3003e1dc2dd1d140a (diff)
downloadpostgresql-325f2ec5557fd1c9156c910102522e04cb42d99c.tar.gz
postgresql-325f2ec5557fd1c9156c910102522e04cb42d99c.zip
Handle heap rewrites even better in logical decoding
Logical decoding should not publish anything about tables created as part of a heap rewrite during DDL. Those tables don't exist externally, so consumers of logical decoding cannot do anything sensible with that information. In ab28feae2bd3d4629bd73ae3548e671c57d785f0, we worked around this for built-in logical replication, but that was hack. This is a more proper fix: We mark such transient heaps using the new field pg_class.relwrite, linking to the original relation OID. By default, we ignore them in logical decoding before they get to the output plugin. Optionally, a plugin can register their interest in getting such changes, if they handle DDL specially, in which case the new field will help them get information about the actual table. Reviewed-by: Craig Ringer <craig@2ndquadrant.com>
Diffstat (limited to 'src/backend/commands/cluster.c')
-rw-r--r--src/backend/commands/cluster.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/backend/commands/cluster.c b/src/backend/commands/cluster.c
index 96a51bb7603..57f3917fdc4 100644
--- a/src/backend/commands/cluster.c
+++ b/src/backend/commands/cluster.c
@@ -692,6 +692,7 @@ make_new_heap(Oid OIDOldHeap, Oid NewTableSpace, char relpersistence,
false,
true,
true,
+ OIDOldHeap,
NULL);
Assert(OIDNewHeap != InvalidOid);