aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2017-05-16 22:57:16 -0400
committerPeter Eisentraut <peter_e@gmx.net>2017-05-16 22:57:16 -0400
commit944dc0f9cec7c3d33648f41aaecfbd976106e975 (patch)
tree62b2499c3f057a28e0f8e7cac96e769929115a3f /src/backend/executor/nodeModifyTable.c
parent0fbfb65d4bfd429651dc28faf3ad1846c965e18d (diff)
downloadpostgresql-944dc0f9cec7c3d33648f41aaecfbd976106e975.tar.gz
postgresql-944dc0f9cec7c3d33648f41aaecfbd976106e975.zip
Check relkind of tables in CREATE/ALTER SUBSCRIPTION
We used to only check for a supported relkind on the subscriber during replication, which is needed to ensure that the setup is valid and we don't crash. But it's also useful to tell the user immediately when CREATE or ALTER SUBSCRIPTION is executed that the relation being added to the subscription is not of a supported relkind. Author: Petr Jelinek <petr.jelinek@2ndquadrant.com> Reported-by: tushar <tushar.ahuja@enterprisedb.com>
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions