On 11 December 2012 10:39, Marko Kreen <mark...@gmail.com> wrote: > On Tue, Dec 11, 2012 at 6:59 AM, Josh Kupershmidt <schmi...@gmail.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
