aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/xml.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2007-01-12 17:04:54 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2007-01-12 17:04:54 +0000
commitd83235415bc22b486180071db0d52c3df8ddc186 (patch)
tree1af64aefba8e01a5d1cab777b376752a7bfab46b /src/backend/utils/adt/xml.c
parentfc568b9d8f6b30d0a5573b73c719e23fa0a6a979 (diff)
downloadpostgresql-d83235415bc22b486180071db0d52c3df8ddc186.tar.gz
postgresql-d83235415bc22b486180071db0d52c3df8ddc186.zip
Add some notes about the basic mathematical laws that the system presumes
hold true for operators in a btree operator family. This is mostly to clarify my own thinking about what the planner can assume for optimization purposes. (blowing dust off an old abstract-algebra textbook...)
Diffstat (limited to 'src/backend/utils/adt/xml.c')
0 files changed, 0 insertions, 0 deletions