Peter Eisentraut <pete...@gmx.net> writes:
> On 10/22/13, 3:40 PM, Tom Lane wrote:
>> In order to avoid having to clutter stuff like that with #ifdef FRONTENDs,
>> I'm now thinking we should use exactly the same names for the frontend and
>> backend versions, ie psprintf() and pvsprintf(). The main reason for
>> considering a pg_ prefix for the frontend versions was to avoid cluttering
>> application namespace; but it's already the case that we don't expect
>> libpgcommon to be namespace clean.
> While this is attractive, the same logic would suggest that we rename
> pg_malloc() to palloc(), and that sounds wrong. The frontend and
> backend functions do have different freeing semantics.
We already crossed that bridge, though, by defining "palloc" in frontend
environments to mean pg_malloc. I'm doubtful that insisting on different
names is going to result in anything except #ifdef clutter.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
