diff options
| author | Peter Geoghegan <pg@bowt.ie> | 2020-03-16 12:00:10 -0700 |
|---|---|---|
| committer | Peter Geoghegan <pg@bowt.ie> | 2020-03-16 12:00:10 -0700 |
| commit | 013c1f6af6c5017d97b1268cf9a5fa3d0575eecb (patch) | |
| tree | 91ce71eaabf6af7bd69da79c93528e150f16ce76 /src/backend/utils/adt/misc.c | |
| parent | fc34b0d9de27ab5ac2887da00b3892bdabd89e45 (diff) | |
| download | postgresql-013c1f6af6c5017d97b1268cf9a5fa3d0575eecb.tar.gz postgresql-013c1f6af6c5017d97b1268cf9a5fa3d0575eecb.zip | |
nbtree: Pass down MAXALIGN()'d itemsz for new item.
Refactor nbtinsert.c so that the final itemsz of each new non-pivot
tuple (the MAXALIGN()'d size) is determined once. Most of the functions
used by leaf page inserts used the insertstate.itemsz value already.
This commit makes everything use insertstate.itemsz as standard
practice. The goal is to decouple tuple size from "effective" tuple
size. Making this distinction isn't truly necessary right now, but that
might change in the future.
Also explain why we consistently apply MAXALIGN() to get an effective
index tuple size. This was rather unclear, in part because it isn't
actually strictly necessary right now.
Diffstat (limited to 'src/backend/utils/adt/misc.c')
0 files changed, 0 insertions, 0 deletions