forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commit2a67d64
committed
Add commentary explaining why MaxIndexTuplesPerPage calculation is safe.
MaxIndexTuplesPerPage ignores the fact that btree indexes sometimesstore tuples with no data payload. But it also ignores the possibilityof "special space" on index pages, which offsets that, so that theresult isn't an underestimate. This all seems worth documenting, though.In passing, remove #define MinIndexTupleSize, which was added bycommit2c03216 but not used in that commit nor later ones.Comment text by me; issue noticed by Peter Geoghegan.Discussion:https://postgr.es/m/CAH2-WzkQmb54Kbx-YHXstRKXcNc+_87jwV3DRb54xcybLR7Oig@mail.gmail.com1 parente013288 commit2a67d64
1 file changed
+9
-1
lines changedLines changed: 9 additions & 1 deletion
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
132 | 132 |
| |
133 | 133 |
| |
134 | 134 |
| |
| 135 | + | |
| 136 | + | |
| 137 | + | |
| 138 | + | |
| 139 | + | |
| 140 | + | |
| 141 | + | |
| 142 | + | |
| 143 | + | |
135 | 144 |
| |
136 |
| - | |
137 | 145 |
| |
138 | 146 |
| |
139 | 147 |
| |
|
0 commit comments
Comments
(0)