Re: Rethinking TupleTableSlot deforming

From: Andres Freund <andres(at)anarazel(dot)de>
To: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
Cc: Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Rethinking TupleTableSlot deforming
Date: 2016-07-22 18:58:10
Message-ID: 20160722185810.5hlmhmfmwipinaun@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-07-22 19:00:32 Re: Rethinking TupleTableSlot deforming
Previous Message Jim Nasby 2016-07-22 18:51:31 Re: Rethinking TupleTableSlot deforming