On Tue, May 6, 2014 at 2:04 PM, Robert Haas <robertmh...@gmail.com> wrote: > I also didn't find anything that looked like our > memory context paradigm, and in particular the ability to cheaply > reset a context, in any other allocator.
You probably knew this but just in case the term for this strategy is called a "ripcord allocator". I believe GCC had one, not sure if it still uses it. I doubt any existing ones are especially helpful though compared to looking at regular allocators and seeing how to integrate them. I assume you're also aware of lock-free data structures and the like. A memory allocator seems like something that needs to be super aware of causing concurrency bottlenecks since it has no idea where it'll be used. -- greg -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
