Re: Rethinking TupleTableSlot deforming - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Rethinking TupleTableSlot deforming
Date
Msg-id 20160722185810.5hlmhmfmwipinaun@alap3.anarazel.de
Whole thread Raw
In response to Re: Rethinking TupleTableSlot deforming  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: Rethinking TupleTableSlot deforming  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
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
solution.




pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Rethinking TupleTableSlot deforming
Next
From: Tom Lane
Date:
Subject: Re: Rethinking TupleTableSlot deforming