Re: [HACKERS] Custom allocators in libpq - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] Custom allocators in libpq
Date
Msg-id 1477dc73-fd46-398e-4abe-e49ce88e8f90@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Custom allocators in libpq  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Custom allocators in libpq  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 8/28/17 15:11, Tom Lane wrote:
> ... but it seems like you're giving up a lot of the possible uses if
> you don't make it apply uniformly.  I admit I'm not sure how we'd handle
> the initial creation of a connection object with a custom malloc.  The
> obvious solution of requiring the functions to be specified at PQconnect
> time seems to require Yet Another PQconnect Variant, which is not very
> appetizing.

I would have expected a separate function just to register the callback
functions, before doing anything else with libpq.  Similar to libxml:
http://xmlsoft.org/xmlmem.html

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Aaron Patterson
Date:
Subject: Re: [HACKERS] Custom allocators in libpq
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Custom allocators in libpq