postgresql/src/backend/lib
Alexander Korotkov 772faafca1 Revert: Implement pg_wal_replay_wait() stored procedure
This commit reverts 06c418e163, e37662f221, bf1e650806, 25f42429e2,
ee79928441, and 74eaf66f98 per review by Heikki Linnakangas.

Discussion: https://postgr.es/m/b155606b-e744-4218-bda5-29379779da1a%40iki.fi
2024-04-11 17:28:15 +03:00
..
Makefile
README
bipartite_match.c
bloomfilter.c
dshash.c Remove unused #include's from backend .c files 2024-03-04 12:02:20 +01:00
hyperloglog.c
ilist.c
integerset.c Remove unused #include's from backend .c files 2024-03-04 12:02:20 +01:00
knapsack.c Remove unused #include's from backend .c files 2024-03-04 12:02:20 +01:00
meson.build
pairingheap.c Revert: Implement pg_wal_replay_wait() stored procedure 2024-04-11 17:28:15 +03:00
rbtree.c

README

This directory contains a general purpose data structures, for use anywhere
in the backend:

binaryheap.c - a binary heap

bipartite_match.c - Hopcroft-Karp maximum cardinality algorithm for bipartite graphs

bloomfilter.c - probabilistic, space-efficient set membership testing

dshash.c - concurrent hash tables backed by dynamic shared memory areas

hyperloglog.c - a streaming cardinality estimator

ilist.c - single and double-linked lists

integerset.c - a data structure for holding large set of integers

knapsack.c - knapsack problem solver

pairingheap.c - a pairing heap

rbtree.c - a red-black tree

stringinfo.c - an extensible string type


Aside from the inherent characteristics of the data structures, there are a
few practical differences between the binary heap and the pairing heap. The
binary heap is fully allocated at creation, and cannot be expanded beyond the
allocated size. The pairing heap on the other hand has no inherent maximum
size, but the caller needs to allocate each element being stored in the heap,
while the binary heap works with plain Datums or pointers.

The linked-lists in ilist.c can be embedded directly into other structs, as
opposed to the List interface in nodes/pg_list.h.