Re: allowing multiple PQclear() calls - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: allowing multiple PQclear() calls
Date
Msg-id CA+U5nML4jNyCGMfXZJ94p7NBxQkVsVL+LrWeS26dd1rVNboPxQ@mail.gmail.com
Whole thread Raw
In response to Re: allowing multiple PQclear() calls  (Boszormenyi Zoltan <zb@cybertec.at>)
Responses Re: allowing multiple PQclear() calls
List pgsql-hackers
On 11 December 2012 12:18, Boszormenyi Zoltan <zb@cybertec.at> wrote:

>>> Such mechanism already exist - you just need to set
>>> your PGresult pointer to NULL after each PQclear().
>>
>> So why doesn't PQclear() do that?
>
>
> Because then PQclear() would need a ** not a *. Do you want its
> interface changed for 9.3 and break compatibility with previous versions?

No, but we should introduce a new public API call that is safer,
otherwise we get people continually re-inventing new private APIs that
Do the Right Thing, as the two other respondents have shown.

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Ibrar Ahmed
Date:
Subject: Re: Review: create extension default_full_version
Next
From: Bruce Momjian
Date:
Subject: Re: Commits 8de72b and 5457a1 (COPY FREEZE)