aboutsummaryrefslogtreecommitdiff
path: root/src/common/binaryheap.c
diff options
context:
space:
mode:
authorMasahiko Sawada <msawada@postgresql.org>2024-04-11 17:04:38 +0900
committerMasahiko Sawada <msawada@postgresql.org>2024-04-11 17:04:38 +0900
commitefb8acc0d05894e0c6c20dfc00513b53098780f0 (patch)
tree471ec23d9ce6731b931527e6fe56ad67b2568590 /src/common/binaryheap.c
parent942219996c632ae9e66c2c4a759e93abc92014ff (diff)
downloadpostgresql-efb8acc0d05894e0c6c20dfc00513b53098780f0.tar.gz
postgresql-efb8acc0d05894e0c6c20dfc00513b53098780f0.zip
Replace binaryheap + index with pairingheap in reorderbuffer.c
A pairing heap can perform the same operations as the binary heap + index, with as good or better algorithmic complexity, and that's an existing data structure so that we don't need to invent anything new compared to v16. This commit makes the new binaryheap functionality that was added in commits b840508644 and bcb14f4abc unnecessary, but they will be reverted separately. Remove the optimization to only build and maintain the heap when the amount of memory used is close to the limit, becuase the bookkeeping overhead with the pairing heap seems to be small enough that it doesn't matter in practice. Reported-by: Jeff Davis Author: Heikki Linnakangas Reviewed-by: Michael Paquier, Hayato Kuroda, Masahiko Sawada Discussion: https://postgr.es/m/12747c15811d94efcc5cda72d6b35c80d7bf3443.camel%40j-davis.com
Diffstat (limited to 'src/common/binaryheap.c')
0 files changed, 0 insertions, 0 deletions