From: Bruce Momjian
These allow uniform resource access by the backend.
- storage/buffer - shared
buffer pool manager
- storage/file - file
manager
- storage/freespace - free
space map
- storage/ipc - semaphores and
shared memory
- storage/large_object
- large objects
- storage/lmgr - lock
manager
- storage/page - page
manager
- storage/smgr - storage/disk
manager
@@ -194,27 +195,27 @@ methods
These control the way data is accessed in heap, indexes, and
transactions.
- access/common - common
access routines
- access/gist - easy-to-define
access method system
- access/hash - hash
- access/heap - heap is use to
store data rows
- access/index - used by all
index types
- access/nbtree - Lehman and
Yao's btree management algorithm
- access/rtree - used for
indexing of 2-dimensional data
- access/transam -
transaction manager (BEGIN/ABORT/COMMIT)
@@ -230,7 +231,7 @@ called nodes. Nodes are generic containers that have a
usually placed in Lists. A List is container with an
elem element, and a next field that points to the
next List. These List structures are chained together
-in a forward linked list. In this way, a chain of Lists can
+in a forward linked list. In this way, a chain of List s can
contain an unlimited number of Node elements, and each
Node can contain any data type. These are used extensively
in the parser, optimizer, and executor to store requests and
@@ -283,9 +284,9 @@ maintained by the backend.
This is used for regular expression handling in the backend, i.e. '~'.
-