Re: rethinking dense_alloc (HashJoin) as a memory context

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: rethinking dense_alloc (HashJoin) as a memory context
Дата
Msg-id 20160713174418.sygesihmyc3upjyh@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: rethinking dense_alloc (HashJoin) as a memory context  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: rethinking dense_alloc (HashJoin) as a memory context  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On 2016-07-13 13:37:55 -0400, Tom Lane wrote:
> I wonder though if we don't already have another similar use-case in
> the ad-hoc "slab allocators" in reorderbuffer.c.

That seems to call more for a general slab allocator design, than for
something like here. After all, there's plenty of freeing ther.e

> We already know that
> that code has performance issues, cf bug #14231, so I suspect there's
> a redesign in its future anyway.

Note that it's not the slab allocators that is having problems, it's
aset.c, iterating through all allocated blocks.

Andres



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: rethinking dense_alloc (HashJoin) as a memory context
Следующее
От: Andres Freund
Дата:
Сообщение: Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold <