mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-08-30 05:17:20 +02:00
PageGetFreeSpace() was being called while not holding the buffer lock, which not only could yield a garbage answer, but even if it's the right answer there might be less space available after we reacquire the buffer lock. Also repair potential deadlock introduced by my recent performance improvement in RelationGetBufferForTuple(): it was possible for two heap_updates to try to lock two buffers in opposite orders. The fix creates a global rule that buffers of a single heap relation should be locked in decreasing block number order. Currently, this only applies to heap_update; VACUUM can get away with ignoring the rule since it holds exclusive lock on the whole relation anyway. However, if we try to implement a VACUUM that can run in parallel with other transactions, VACUUM will also have to obey the lock order rule. |
||
---|---|---|
.. | ||
access | ||
bootstrap | ||
catalog | ||
commands | ||
executor | ||
lib | ||
libpq | ||
main | ||
nodes | ||
optimizer | ||
parser | ||
port | ||
postmaster | ||
regex | ||
rewrite | ||
storage | ||
tcop | ||
tioga | ||
utils | ||
Makefile |