Andres Freund <and...@2ndquadrant.com> writes:
> To what extent do you want palloc et al. emulation? Provide actual pools
> or just make redirect to malloc and provide the required symbols (at the
> very least CurrentMemoryContext)?
I don't see any need for memory pools, at least not for frontend
applications of the currently envisioned levels of complexity. I concur
with Alvaro's suggestion about just #define'ing them to malloc/free ---
or maybe better, pg_malloc/free so that we can have a failure-checking
wrapper.
Not sure how we ought to handle elog, but maybe we can put off that bit
of design until we have a more concrete use-case.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
