Re: Concurrent deadlock scenario with DROP INDEX on partitioned index
Jimmy Yih <jyih@vmware.com>
From: Jimmy Yih <jyih@vmware.com>
To: Zhihong Yu <zyu@yugabyte.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Gaurab Dey <gaurabd@vmware.com>
Date: 2022-03-16T20:43:12Z
Lists: pgsql-hackers
Attachments
- v3-0001-Fix-concurrent-deadlock-scenario-with-DROP-INDEX-.patch (application/octet-stream) patch v3-0001
Zhihong Yu <zyu@yugabyte.com> wrote: > Hi, > For RangeVarCallbackForDropRelation(): > > + LockRelationOid(indexRelationOid, heap_lockmode); > > Since the above is called for both if and else blocks, it can be lifted outside. Thanks for the feedback. Attached new v3 patch with feedback addressed. -- Jimmy Yih (VMware) Gaurab Dey (VMware)
Commits
-
Fix risk of deadlock failure while dropping a partitioned index.
- d8d378d5100f 12.11 landed
- b8ae17fd9fdf 11.16 landed
- 7b6ec86532c2 15.0 landed
- 2241e5ceda2f 13.7 landed
- 05ccf974cd75 14.3 landed