| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Marko Kreen <markokr(at)gmail(dot)com> |
| Cc: | Josh Kupershmidt <schmiddy(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: allowing multiple PQclear() calls |
| Date: | 2012-12-11 11:45:13 |
| Message-ID: | CA+U5nML7ecex7oF83HGvozc=ww97fkcUvMSv7eXYgCNx437LKQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11 December 2012 10:39, Marko Kreen <markokr(at)gmail(dot)com> wrote:
> On Tue, Dec 11, 2012 at 6:59 AM, Josh Kupershmidt <schmiddy(at)gmail(dot)com> wrote:
>> Would it be crazy to add an "already_freed" flag to the pg_result
>> struct which PQclear() would set, or some equivalent safety mechanism,
>> to avoid this hassle for users?
>
> Such mechanism already exist - you just need to set
> your PGresult pointer to NULL after each PQclear().
So why doesn't PQclear() do that?
Maintaining a pointer to something that no longer exists seems strange.
Under what conditions would anybody want the old pointer value after PQclear() ?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Boszormenyi Zoltan | 2012-12-11 12:18:27 | Re: allowing multiple PQclear() calls |
| Previous Message | Pavel Stehule | 2012-12-11 11:15:23 | skipping context for RAISE statements - maybe obsolete? |