pgsql: Fix possible "tuple concurrently updated" error in ALTER TABLE. - Mailing list pgsql-committers

From Robert Haas
Subject pgsql: Fix possible "tuple concurrently updated" error in ALTER TABLE.
Date
Msg-id E1Q0lel-0003LF-5E@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix possible "tuple concurrently updated" error in ALTER TABLE.

When adding an inheritance parent to a table, an AccessShareLock on the
parent isn't strong enough to prevent trouble, so take
ShareUpdateExclusiveLock instead.  Since this is a behavior change,
albeit a fairly unobtrusive one, and since we have only one report
from the field, no back-patch.

Report by Jon Nelson, analysis by Alvaro Herrera, fix by me.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/fbcf4b92aa64d4577bcf25925b055316b978744a

Modified Files
--------------
src/backend/commands/tablecmds.c |   15 +++++++++++----
1 files changed, 11 insertions(+), 4 deletions(-)


pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: pgsql: Move synchronous_standbys_defined updates from WAL writer to BG
Next
From: Andrew Dunstan
Date:
Subject: Re: pgsql: Document the all-balls IPv6 address.