public inbox for [email protected]
help / color / mirror / Atom feedFrom: Peter Eisentraut <[email protected]>
To: Amit Kapila <[email protected]>
To: Alvaro Herrera <[email protected]>
Cc: Tomas Vondra <[email protected]>
Cc: Rahila Syed <[email protected]>
Cc: Peter Smith <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Column Filtering in Logical Replication
Date: Fri, 17 Dec 2021 08:03:33 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAA4eK1+WTJ-MXXV23Nva2rR+mBs2wCPakHFUhvLi9rHsBiT8FQ@mail.gmail.com>
References: <[email protected]>
<[email protected]>
<CAA4eK1+WTJ-MXXV23Nva2rR+mBs2wCPakHFUhvLi9rHsBiT8FQ@mail.gmail.com>
On 17.12.21 05:47, Amit Kapila wrote:
> I think in the above sentence, you mean to say "dropped from the
> publication". So, IIUC, you are proposing that if one drops a column
> that was part of the column list of a relation in a publication, an
> error will be raised. Also, if the user specifies CASCADE in Alter
> Table ... Drop Column, then we drop the relation from publication. Is
> that right? BTW, this is somewhat on the lines of what row_filter
> patch is also doing where if the user drops the column that was part
> of row_filter for a relation in publication, we give an error and if
> the user tries to drop the column with CASCADE then the relation is
> removed from the publication.
That looks correct. Consider how triggers behave: Dropping a column
that a trigger uses (either in UPDATE OF or a WHEN condition) errors
with RESTRICT and drops the trigger with CASCADE.
view thread (167+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Column Filtering in Logical Replication
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox