postgresql/src/backend/lib
Peter Eisentraut a06e56b247 doc: Update redirecting links
Update links that resulted in redirects.  Most are changes from http to
https, but there are also some other minor edits.  (There are still some
redirects where the target URL looks less elegant than the one we
currently have.  I have left those as is.)
2018-07-16 10:48:05 +02:00
..
binaryheap.c Update copyright for 2018 2018-01-02 23:30:12 -05:00
bipartite_match.c doc: Update redirecting links 2018-07-16 10:48:05 +02:00
bloomfilter.c Post-feature-freeze pgindent run. 2018-04-26 14:47:16 -04:00
dshash.c Minor clean-up in dshash.{c,h}. 2018-03-01 16:25:46 -08:00
hyperloglog.c Update copyright for 2018 2018-01-02 23:30:12 -05:00
ilist.c Update copyright for 2018 2018-01-02 23:30:12 -05:00
knapsack.c Remove some inappropriate #includes. 2018-02-16 12:14:08 -05:00
Makefile Add Bloom filter implementation. 2018-03-31 17:49:41 -07:00
pairingheap.c Update copyright for 2018 2018-01-02 23:30:12 -05:00
rbtree.c Update copyright for 2018 2018-01-02 23:30:12 -05:00
README Add missing files to src/backend/lib/README. 2018-05-22 13:25:28 +03:00
stringinfo.c Update copyright for 2018 2018-01-02 23:30:12 -05:00

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

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.