| From: | Mani Sankar <manisankar01695(at)gmail(dot)com> |
|---|---|
| To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Марат Гасанян <marat_gasanyan(at)mail(dot)ru>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Problem with constraint unique. |
| Date: | 2024-12-12 18:44:22 |
| Message-ID: | CAEtVwW0BnQVvNrnH0hckfNk8rTB-Q+dD1RVxXrtnZpMxxEAirg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Yeah correct got confused with PK and FK
Thanks, for correcting
Regards,
Mani.
On Fri, 13 Dec, 2024, 12:05 am Greg Sabino Mullane, <htamfids(at)gmail(dot)com>
wrote:
> On Thu, Dec 12, 2024 at 12:52 PM Mani Sankar <manisankar01695(at)gmail(dot)com>
> wrote:
>
>> One possible reason I can think of is setting the
>> session_replication_role to replica do some insert that violates the
>> constraints and then set it back to orgin.
>>
>
> session_replication_role can disable triggers and rules, but primary keys
> will still be enforced.
>
> Cheers,
> Greg
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-12-12 21:55:42 | Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails |
| Previous Message | Greg Sabino Mullane | 2024-12-12 18:34:49 | Re: Problem with constraint unique. |