Re: Ordered Append Node

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: Ordered Append Node
Дата
Msg-id 47469D42.7040003@enterprisedb.com
обсуждение исходный текст
Ответ на Re: Ordered Append Node  (Markus Schiltknecht <markus@bluegap.ch>)
Ответы Re: Ordered Append Node  (Markus Schiltknecht <markus@bluegap.ch>)
Re: Ordered Append Node  (Gregory Stark <stark@enterprisedb.com>)
Список pgsql-hackers
Markus Schiltknecht wrote:
> Florian Weimer wrote:
>>> Given the partitioning case, I'd expect all rows to have an equal
>>> tuple descriptor. Maybe this is a matter of what to optimize, then?
>>>
>>> Could you elaborate on what use case you have in mind?
>>
>> You need a priority queue to figure out from which tape (partition)
>> you need to remove the next tuple.
> 
> And why do you need lots of heap memory to do that? Anything wrong with 
> the zipper approach I've outlined upthread?

We're talking about a binary heap, with just one node per partition. 
AFAICT it's roughly the same data structure as the zipper tree you 
envisioned, but not implemented with separate executor nodes for each level.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Markus Schiltknecht
Дата:
Сообщение: Re: Ordered Append Node
Следующее
От: Florian Weimer
Дата:
Сообщение: Re: Ordered Append Node