Re: Relations being opened without any lock whatever
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2018-10-01T00:08:28Z
Lists: pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes: > Okay, that's bad. Wouldn't it be sufficient to use what the caller > passes out as lockmode instead of enforcing AEL though? No, because at the bottom of that function we're going to do a DROP CONSTRAINT on the old FK constraint, and that needs AEL anyway. If we tried to take a lesser lock first we'd just be creating a lock-upgrade deadlock risk. regards, tom lane
Commits
-
Fix tuple_data_split() to not open a relation without any lock.
- ec5f71aeadf9 9.6.11 landed
- b66827ca7c5a 12.0 landed
- 370b28ccd430 10.6 landed
- 1f25c7a8fc99 11.0 landed
-
Lock relation used to generate fresh data for RMV.
- de0bea8d4d81 9.3.25 landed
-
Fix ALTER COLUMN TYPE to not open a relation without any lock.
- db01fc97ad80 10.6 landed
- 26318c4b858a 9.4.20 landed
- 0360c539f2a2 9.6.11 landed
- 00d00b5b0d12 9.3.25 landed
- 0031e9d6ab80 9.5.15 landed
- e27453bd839f 12.0 landed
- 4c985549fe82 11.0 landed