Re: Rethinking TupleTableSlot deforming

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: Rethinking TupleTableSlot deforming
Дата
Msg-id 20160722185810.5hlmhmfmwipinaun@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: Rethinking TupleTableSlot deforming  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Ответы Re: Rethinking TupleTableSlot deforming  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Список 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 по дате отправления:

Предыдущее
От: Jim Nasby
Дата:
Сообщение: Re: Rethinking TupleTableSlot deforming
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Rethinking TupleTableSlot deforming