| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Exposing guc_malloc/strdup/realloc for plugins? |
| Date: | 2018-05-08 06:46:12 |
| Message-ID: | 20180508064612.GA11897@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi all,
While hacking on an extension, I have finished by doing things similar
to guc_malloc & friends for the allocation of a GUC parameter for malloc
portability. While that's not really a big deal to copy/paste this
code, I am wondering if it would make sense to expose them for extension
developers. Please see the attached for the simple idea.
Thanks,
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| guc-alloc-extern.patch | text/x-diff | 1.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2018-05-08 07:07:41 | Re: [Suspect SPAM] Re: [HACKERS] path toward faster partition pruning |
| Previous Message | Alexander Lakhin | 2018-05-08 06:42:23 | Re: Porting PG Extension from UNIX to Windows |