Re: PATCH: two slab-like memory allocators

From: John Gorman <johngorman2(at)gmail(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: Petr Jelinek <petr(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PATCH: two slab-like memory allocators
Date: 2016-10-05 10:40:43
Message-ID: CALkS6B_=b7i4-TH-8CuDWZ98TZz=zU07F-Z81kKPgg-kKgcwBg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 4, 2016 at 10:11 PM, Tomas Vondra

For GenSlab the situation is less clear, as there probably are ways to make
> it work, but I'd vote to keep it simple for now, and simply do elog(ERROR)
> in the realloc() methods - both for Slab and GenSlab. The current use case
> (reorderbuffer) does not need that, and it seems like a can of worms to me.

Good plan. Realloc can be added later if there is an actual use case.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2016-10-05 11:02:07 Re: Hash tables in dynamic shared memory
Previous Message Thomas Munro 2016-10-05 10:28:35 Re: Dynamic shared memory areas