aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/xml.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-10-11 18:40:53 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2011-10-11 18:40:53 -0400
commit8c8ba6d11b06e5a8b9fe5653a1cd17c437af5f7b (patch)
treec3a34c5dbafbba2e3e8fcee0482e7cfeaff849bb /src/backend/utils/adt/xml.c
parentcb6771fb32cbdb11c8d84b7d62ee940bdba38d52 (diff)
downloadpostgresql-8c8ba6d11b06e5a8b9fe5653a1cd17c437af5f7b.tar.gz
postgresql-8c8ba6d11b06e5a8b9fe5653a1cd17c437af5f7b.zip
Add comment on why pulling data from a "name" index column can't crash.
It's been bothering me for several days that pretending that the cstring data stored in a btree name_ops column is really a "name" Datum could lead to reading past the end of memory. However, given the current memory layout used for index-only scans in the btree code, a crash is in fact not possible. Document that so we don't break it. I have not thought of any other solutions that aren't fairly ugly too, and most of them lose the functionality of index-only scans on name columns altogether, so this seems like the way to go.
Diffstat (limited to 'src/backend/utils/adt/xml.c')
0 files changed, 0 insertions, 0 deletions