Re: Re: custom hash-based COUNT(DISTINCT) aggregate - unexpectedly high memory consumption

Поиск
Список
Период
Сортировка
От Tomas Vondra
Тема Re: Re: custom hash-based COUNT(DISTINCT) aggregate - unexpectedly high memory consumption
Дата
Msg-id 5253215C.1050500@fuzzy.cz
обсуждение исходный текст
Ответ на Re: Re: custom hash-based COUNT(DISTINCT) aggregate - unexpectedly high memory consumption  (Atri Sharma <atri.jiit@gmail.com>)
Ответы Re: Re: custom hash-based COUNT(DISTINCT) aggregate - unexpectedly high memory consumption  (Atri Sharma <atri.jiit@gmail.com>)
Список pgsql-hackers
Hi Atri!

On 7.10.2013 16:56, Atri Sharma wrote:
>>> 3. Consider dropping buckets in favor of open addressing (linear
>>> probing, quadratic, whatever).  This avoids another level of
>>> pointer indirection.
>> 
>> OK, this sounds really interesting. It should be fairly
>> straightforward for fixed-length data types (in that case I can get
>> rid of the pointers altogether).
>> 
> Consider the aspects associated with open addressing.Open addressing
> can quickly lead to growth in the main table.Also, chaining is a much
> cleaner way of collision resolution,IMHO.

What do you mean by "growth in the main table"?

Tomas



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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: mvcc catalo gsnapshots and TopTransactionContext
Следующее
От: Heikki Linnakangas
Дата:
Сообщение: Re: space reserved for WAL record does not match what was written: panic on windows