On 7/22/16 1:58 PM, Andres Freund wrote:
On 2016-07-22 13:51:31 -0500, Jim Nasby wrote:
Another option would be to remember the
tuple offsets (NOT attcacheoff) that have
been computed as well as whether a
varlena attribute has actually been
deformed. That eliminates the need to
pre-declare what attributes you're
allowed to reference.

That'd make access more expensive, so that doesn't seem a very enticing

Yeah, it's certainly a tradeoff. The advantage is this might be less invasive; it might also work in more cases like heap_deform_tuple (which I think is used a lot more than table slots).

It's certainly possible it's not worth it, but I wanted to put the idea out there.
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)   mobile: 512-569-9461

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to