On Wed, Sep 09, 2026 at 01:14:54PM -0400, Greg Burd wrote: > That should say the concern does reproduce. Robert's worry was that some > tuples storable today would not be storable at all once the TOAST pointer > gets wider, and that is what the table right below that sentence shows. At > 370 text columns set STORAGE EXTERNAL, oid stores the row and oid8 fails > with "row is too big: size 8824, maximum size 8160". The ceiling on > out-of-line attributes per row drops from about 453 to about 366.
Thanks for the exact numbers. 366 toast columns still looks like an insane thing to do, so I am not much concerned by somebody having a number of toast attributes in the [366,453[ range that worked with a TOAST table based on oid, then trying to do a rewrite to a new toast table based on oid8 to see the load of data fail suddenly. > Doesn't change where I land, still +1 on the series, and I think this is > the one cost that deserves a sentence in the docs next to the reloption. Hmm. Okay. I'll think about something here. -- Michael
signature.asc
Description: PGP signature
