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
Ответ на
Список
Дерево обсуждения
rethinking dense_alloc (HashJoin) as a memory context Tomas Vondra <tomas.vondra@2ndquadrant.com>
Re: rethinking dense_alloc (HashJoin) as a memory context Peter Geoghegan <pg@heroku.com>
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 Andres Freund <andres@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 Tomas Vondra <tomas.vondra@2ndquadrant.com>
Re: rethinking dense_alloc (HashJoin) as a memory context Robert Haas <robertmhaas@gmail.com>
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 Andres Freund <andres@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 Robert Haas <robertmhaas@gmail.com>
Re: rethinking dense_alloc (HashJoin) as a memory context Greg Stark <stark@mit.edu>
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 Robert Haas <robertmhaas@gmail.com>
Re: rethinking dense_alloc (HashJoin) as a memory context Peter Geoghegan <pg@heroku.com>
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
Дата:
От: Andres Freund
Дата:
FAQ