]> granicus.if.org Git - postgresql/commit
Reconsider page size for large objects: rather than stuffing disk pages
authorTom Lane <tgl@sss.pgh.pa.us>
Tue, 24 Oct 2000 03:34:53 +0000 (03:34 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Tue, 24 Oct 2000 03:34:53 +0000 (03:34 +0000)
commita9b6b01ee8a70d6abe8e5a56f18115c804fd10f4
tree3e90a8b6586d57e5233bb6de36d39db1f441e263
parent711c9f30f80fa8756fb7b04b3d49a85e8ecad539
Reconsider page size for large objects: rather than stuffing disk pages
as full as possible, seems better to use a tuple size around BLCKSZ/4
so that less space is wasted when a LO tuple is updated.  Also, this
lets us use a logical page size that's an exact power of two, avoiding
partial-page writes when client is sending us stuff in power-of-2
buffer chunks.
src/include/catalog/catversion.h
src/include/storage/large_object.h