]> granicus.if.org Git - postgresql/commit
Fix intermittent crash in DROP INDEX CONCURRENTLY.
authorTom Lane <tgl@sss.pgh.pa.us>
Thu, 6 Dec 2012 04:42:55 +0000 (23:42 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Thu, 6 Dec 2012 04:42:55 +0000 (23:42 -0500)
commit4863ed8f372f2d38f1870fb668b8a99097223cf7
treea0c1cef4eca8ead417f91a322316bdf9dea92b63
parent161021dd4cc467277575533af7ce5274c0ea43d7
Fix intermittent crash in DROP INDEX CONCURRENTLY.

When deleteOneObject closes and reopens the pg_depend relation,
we must see to it that the relcache pointer held by the calling function
(typically performMultipleDeletions) is updated.  Usually the relcache
entry is retained so that the pointer value doesn't change, which is why
the problem had escaped notice ... but after a cache flush event there's
no guarantee that the same memory will be reassigned.  To fix, change
the recursive functions' APIs so that we pass around a "Relation *"
not just "Relation".

Per investigation of occasional buildfarm failures.  This is trivial
to reproduce with -DCLOBBER_CACHE_ALWAYS, which points up the sad
lack of any buildfarm member running that way on a regular basis.
src/backend/catalog/dependency.c