postgresql/src/backend/lib
Alexander Korotkov 8d51d7f403 Use C99 designator in the rbtree sentinel definition
This change should improve the code readability.

Discussion: https://postgr.es/m/CAGRrpzYE8-7GCoaPjOiL9T_HY605MRax-2jgTtLq236uksZ1Sw%40mail.gmail.com
Author: Steve Chavez, Alexander Korotkov
Reviewed-by: Alexander Korotkov
2022-07-08 22:00:03 +03:00
..
Makefile Make StringInfo available to frontend code. 2019-11-05 14:56:40 -08:00
README Add IntegerSet, to hold large sets of 64-bit ints efficiently. 2019-03-22 13:21:45 +02:00
binaryheap.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
bipartite_match.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
bloomfilter.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
dshash.c Pre-beta mechanical code beautification. 2022-05-12 15:17:30 -04:00
hyperloglog.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
ilist.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
integerset.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
knapsack.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
pairingheap.c Update copyright for 2022 2022-01-07 19:04:57 -05:00
rbtree.c Use C99 designator in the rbtree sentinel definition 2022-07-08 22:00:03 +03:00

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.