| From: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Exposing guc_malloc/strdup/realloc for plugins? |
| Date: | 2018-05-08 14:02:48 |
| Message-ID: | CAHE3wgi9a7QGPiEwB1f8XEXHw+f=OOQPOsvMXyGEges7=z3OMw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2018-05-08 3:46 GMT-03:00 Michael Paquier <michael(at)paquier(dot)xyz>:
> 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.
>
Although I didn't need similar code on some extensions, code reuse is
always a good goal.
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2018-05-08 14:06:25 | Re: perlcritic and perltidy |
| Previous Message | Teodor Sigaev | 2018-05-08 13:56:31 | Re: Cast jsonb to numeric, int, float, bool |