| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Aaron Patterson <tenderlove(at)ruby-lang(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Custom allocators in libpq |
| Date: | 2017-08-28 21:04:20 |
| Message-ID: | 1477dc73-fd46-398e-4abe-e49ce88e8f90@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-08-28 21:15:17 | Re: Custom allocators in libpq |
| Previous Message | Aaron Patterson | 2017-08-28 19:59:20 | Re: Custom allocators in libpq |