| From: | Jan Wieck <jan(at)wi3ck(dot)info> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com> |
| Cc: | Perry Smith <pedz(at)easesoftware(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: What have I done!?!?!? :-) |
| Date: | 2022-04-08 13:07:39 |
| Message-ID: | 8242bf5f-acad-34f9-57cf-5424192a3e0d@wi3ck.info |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 4/8/22 08:58, Magnus Hagander wrote:
> A side-note on this, which of course won't help the OP at this point,
> but if the general best practice of not running the application with a
> highly privileged account is followed, the problem won't occur (it will
> just fail early before breaking things). DISABLE TRIGGER ALL requires
> either ownership of the table or superuser permissions, none of which
> it's recommended that the application run with. Doesn't help once the
> problem has occurred of course, but can help avoid it happening in the
> future.
It gets even better further down in that code, where it UPDATEs
pg_constraint directly. That not only requires superuser but also catupd
permissions (which are separate from superuser for a reason).
Regards, Jan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2022-04-08 13:10:40 | Re: What have I done!?!?!? :-) |
| Previous Message | Magnus Hagander | 2022-04-08 13:07:28 | Re: How to get updated order data |