| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: #XX000: ERROR: tuple concurrently updated |
| Date: | 2025-02-24 15:01:51 |
| Message-ID: | 1337154.1740409311@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Dominique Devienne <ddevienne(at)gmail(dot)com> writes:
> But during those "restore" transactions, I must also make role-to-role
> grants,
> which AFAIK involve adding rows to pg_auth_members. So they are not subject
> to the same "no support for concurrent updates in the catalog-manipulation"
> you mentioned, as schema-to-role grants are, right? Because that's an
> insert,
> not an update? Just want to make sure, as I'm thinking how to change our
> code.
Yeah, I think "GRANT role" should be relatively immune to that
problem, as long as you're making distinct grants (not same
grantor/grantee/granted roles). Wouldn't hurt to test.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2025-02-24 15:10:06 | Re: COLLATION update in 13.1 |
| Previous Message | Ron Johnson | 2025-02-24 14:59:00 | Re: COLLATION update in 13.1 |