| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Chris Travers <chris(dot)travers(at)adjust(dot)com> |
| Cc: | nickb <nickb(at)imap(dot)cc>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ERROR: tuple concurrently updated when modifying privileges |
| Date: | 2019-05-14 07:11:53 |
| Message-ID: | 20190514071153.GA1376@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, May 14, 2019 at 08:08:05AM +0200, Chris Travers wrote:
> Having thought about this a bit, I think the best solution would be to have
> grant take out an access share lock to the tables granted. This would
> prevent concurrent alter table operations from altering the schema
> underneath the grant as well, and thus possibly cause other race conditions.
>
> Any thoughts?
"tuple concurrently updated" is an error message which should never be
user-facing, and unfortunately there are many scenarios where it can
be triggered by playing with concurrent DDLs:
https://postgr.es/m/20171228063004.GB6181@paquier.xyz
If you have an idea of patch, could you write it? Having an isolation
test case would be nice as well.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | navneet nikku | 2019-05-14 07:41:37 | can we create index/constraints in different schema |
| Previous Message | Thomas Munro | 2019-05-14 06:58:14 | Re: Tab completion for CREATE TYPE |