| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | André Kutepow <a(dot)kutepow(at)prodat-sql(dot)de> |
| Cc: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #18019: misbehaviour by replication |
| Date: | 2023-07-13 10:28:49 |
| Message-ID: | CAA4eK1JJbjg5wagqWbyEjL2Jz3haCG4jSXTvRoFTrhxjd9SQbA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Jul 13, 2023 at 2:33 PM André Kutepow <a(dot)kutepow(at)prodat-sql(dot)de> wrote:
>
> > When you updated that filter column from TRUE to FALSE, we think you hoped that it would not replicate.
> no, I hoped thar it would replicate, but I was hoping to get an error in
> the log that this was not possible, since this record is referenced from
> another table and cannot be simply deleted, what we see by a regular
> DELETE attempt
>
By default, triggers are not enabled while applying the changes on the
subscriber side. You can use Alter Table .. Enable Trigger command to
enable it as mentioned in docs [1] as well (The apply process on the
subscriber ...).
[1] - https://www.postgresql.org/docs/devel/logical-replication-architecture.html
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2023-07-13 10:30:40 | Re: BUG #18019: misbehaviour by replication |
| Previous Message | André Kutepow | 2023-07-13 09:03:37 | Re: BUG #18019: misbehaviour by replication |