postgresql/src/backend/lib
Heikki Linnakangas 955557ddcc Move rbtree.c from src/backend/utils/misc to src/backend/lib.
We have other general-purpose data structures in src/backend/lib, so it
seems like a better home for the red-black tree as well.
2014-12-22 17:52:08 +02:00
..
binaryheap.c Misc comment typo fixes. 2014-12-16 16:37:46 +02:00
ilist.c Fix typos in comments. 2014-03-17 20:47:28 +09:00
Makefile Move rbtree.c from src/backend/utils/misc to src/backend/lib. 2014-12-22 17:52:08 +02:00
pairingheap.c Use a pairing heap for the priority queue in kNN-GiST searches. 2014-12-22 12:05:57 +02:00
rbtree.c Move rbtree.c from src/backend/utils/misc to src/backend/lib. 2014-12-22 17:52:08 +02:00
README Move rbtree.c from src/backend/utils/misc to src/backend/lib. 2014-12-22 17:52:08 +02:00
stringinfo.c pgindent run for 9.4 2014-05-06 12:12:18 -04:00

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

binaryheap.c - a binary heap

pairingheap.c - a pairing heap

rbtree.c - a red-black tree

ilist.c - single and double-linked lists.

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.