diff options
| author | Amit Kapila <akapila@postgresql.org> | 2022-09-23 08:21:26 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2022-09-23 08:21:26 +0530 |
| commit | 13a185f54ba594a5fb42bac3e1ecbdfd62b9041f (patch) | |
| tree | 4e4c8ec85d8b075b44517a1981fa22332f8f5c0d /src/backend/commands/dbcommands.c | |
| parent | d89755dac6153518a601ca0fa9e489f2bc209fdc (diff) | |
| download | postgresql-13a185f54ba594a5fb42bac3e1ecbdfd62b9041f.tar.gz postgresql-13a185f54ba594a5fb42bac3e1ecbdfd62b9041f.zip | |
Allow publications with schema and table of the same schema.
We previously thought that allowing such cases can confuse users when they
specify DROP TABLES IN SCHEMA but that doesn't seem to be the case based
on discussion. This helps to uplift the restriction during
ALTER TABLE ... SET SCHEMA which used to ensure that we couldn't end up
with a publication having both a schema and the same schema's table.
To allow this, we need to forbid having any schema on a publication if
column lists on a table are specified (and vice versa). This is because
otherwise we still need a restriction during ALTER TABLE ... SET SCHEMA to
forbid cases where it could lead to a publication having both a schema and
the same schema's table with column list.
Based on suggestions by Peter Eisentraut.
Author: Hou Zhijie and Vignesh C
Reviewed-By: Peter Smith, Amit Kapila
Backpatch-through: 15, where it was introduced
Discussion: https://postgr.es/m/2729c9e2-9aac-8cda-f2f4-34f2bcc18f4e@enterprisedb.com
Diffstat (limited to 'src/backend/commands/dbcommands.c')
0 files changed, 0 insertions, 0 deletions