Re: Reasons not to like asprintf - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Reasons not to like asprintf
Date
Msg-id 20131022195035.GD4987@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: Reasons not to like asprintf  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Reasons not to like asprintf  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> ... BTW, another reason to choose identical APIs for frontend and backend
> versions of these functions is that it greatly eases use of them in shared
> frontend/backend code.  As I notice somebody has *already done* in
> common/relpath.c.   I'm not exactly sure how those psprintf calls are
> working at all in frontend builds.

There's psprintf in src/common/fe_memutils.c, too, using the backend's
API, which is why this works.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Reasons not to like asprintf
Next
From: Andres Freund
Date:
Subject: Re: Failure while inserting parent tuple to B-tree is not fun