Files
postgresql/src
Tom Lane 68f7b91e50 In rebuild_relation(), don't access an already-closed relcache entry.
This reliably fails with -DRELCACHE_FORCE_RELEASE, as reported by
Andrew Dunstan, and could sometimes fail in normal operation, resulting
in a wrong persistence value being used for the transient table.
It's not immediately clear to me what effects that might have beyond
the risk of a crash while accessing OldHeap->rd_rel->relpersistence,
but it's probably not good.

Bug introduced by commit f41872d0c, and made substantially worse by
commit 85b506bbf, which added a second such access significantly
later than the heap_close.  I doubt the first reference could fail
in a production scenario, but the second one definitely could.

Discussion: https://postgr.es/m/7b52f900-0579-cda9-ae2e-de5da17090e6@2ndQuadrant.com
2017-03-04 16:09:33 -05:00
..
2017-02-18 13:46:03 +01:00
2016-06-09 18:02:36 -04:00
2016-01-28 16:47:36 +09:00
2017-02-06 16:45:25 -05:00
2017-03-01 14:02:06 -05:00
2016-01-02 13:33:40 -05:00
2017-02-06 11:34:15 +02:00