Re: [PATCH 2/5] Make relpathbackend return a statically result instead of palloc()'ing it
От | Tom Lane |
---|---|
Тема | Re: [PATCH 2/5] Make relpathbackend return a statically result instead of palloc()'ing it |
Дата | |
Msg-id | 27570.1357676843@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [PATCH 2/5] Make relpathbackend return a statically result instead of palloc()'ing it (Andres Freund <andres@2ndquadrant.com>) |
Ответы |
Re: [PATCH 2/5] Make relpathbackend return a statically
result instead of palloc()'ing it
Re: [PATCH 2/5] Make relpathbackend return a statically result instead of palloc()'ing it [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4) |
Список | pgsql-hackers |
Andres Freund <andres@2ndquadrant.com> writes: > Uhm, we don't have & need palloc support and I don't think > relpathbackend() is a good justification for adding it. I've said from the very beginning of this effort that it would be impossible to share any meaningful amount of code between frontend and backend environments without adding some sort of emulation of palloc/pfree/elog. I think this patch is just making the code uglier and more fragile to put off the inevitable, and that we'd be better served to bite the bullet and do that. regards, tom lane
В списке pgsql-hackers по дате отправления: