Heikki Linnakangas <heikki@enterprisedb.com> writes:
> On second thought, expanding AttrNumber to int32, wholesale, might not
> be a good idea,
No, it wouldn't. For one thing it'd be a protocol break --- column
numbers are int16 --- and for another, we'd have terrible performance
problems with such wide rows. Actually rows are supposed to be limited
to ~1600 columns, anyway, because of HeapTupleHeader limitations.
Apparently you've found a path where that restriction isn't enforced
correctly, but I haven't seen the referenced message yet ...
regards, tom lane
