From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | John Gorman <johngorman2(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PATCH: two slab-like memory allocators |
Date: | 2016-10-25 22:57:59 |
Message-ID: | 08542375-63f8-db53-daa0-f73745fdaa00@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/25/16 4:48 PM, Tomas Vondra wrote:
> The main issue that bugs me is the name of the Gen allocator, but I
> don't have a good naming ideas :( The basic characteristics of Gen is
> that it does not reuse space released by pfree(), relying on the fact
> that the whole block will become free. That should be reflected in the
> name somehow, I guess.
OneTime? OneUse? OneShot? AllocOnce?
OneHitWonder? ;P
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2016-10-26 00:41:13 | Re: Wraparound warning |
Previous Message | Chapman Flack | 2016-10-25 22:56:28 | 9.6, background worker processes, and PL/Java |