From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | salmanbasmechi(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17993: FK issue on logical replication table |
Date: | 2023-06-26 04:42:30 |
Message-ID: | CAA4eK1KMAUWfmS4_kZS=Ca09+T3bM-XJZLyefkciWf4cDSzKjg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Sun, Jun 25, 2023 at 12:57 AM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
>
> Finally, it seems FK constraint does not apply in replication and delete
> signal from publisher can remove any referenced data in subscriber.
> In your docs there is not any line that notice this behavior, and if it is
> normal, please update your docs and notify me by email.
>
Isn't the behavior you are seeing is same as what is documented in the
description of GUC "session_replication_role"? See [1]. You might want
to set the value of "session_replication_role" as origin/local to see
if that works for your use case.
[1] - https://www.postgresql.org/docs/devel/runtime-config-client.html
--
With Regards,
Amit Kapila.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2023-06-26 04:56:42 | Re: BUG #17995: Segmentation fault caused by UPDATE statement |
Previous Message | Tom Lane | 2023-06-26 04:27:08 | Re: BUG #17995: Segmentation fault caused by UPDATE statement |