Postgres Pro
Downloads
Home   >   mailing lists

Re: LibPQ: Lifetime of PGresult passed in to PQnoticeReceiver callback - Mailing list pgsql-general

From Dominique Devienne
Subject Re: LibPQ: Lifetime of PGresult passed in to PQnoticeReceiver callback
Date
Msg-id CAFCRh-971bjYCb3NYWaAYSscDJXnZTVc=24gW8AOaZnRLCrQFQ@mail.gmail.com
Whole thread Raw
In response to LibPQ: Lifetime of PGresult passed in to PQnoticeReceiver callback  (Dominique Devienne <ddevienne@gmail.com>)
List pgsql-general
Tree view
Hi again. Is this not the right ML?
Which PostgreSQL ML should this question be asked to, to have a chance to get an answer?
I'm new to this particular ML, and I'm surprised by the silence. Thanks, --DD

On Mon, Dec 13, 2021 at 9:46 AM Dominique Devienne <ddevienne@gmail.com> wrote:
Hi,

The doc at https://www.postgresql.org/docs/current/libpq-notice-processing.html is not clear to me on whether it should be PQclear'd or not. Who manages the lifetime of that PGresult?

Also, the "could be called as long as either the PGconn or PGresult exist" mention,
implies we do not need to clear the notice callback before PQfinish'ing the connection.
(and that does not seem possible, given passing in a NULL pointer is just a *get* it seems).
Is that correct?

Yet we are seeing our notice callback being called with an invalid PGresult (i.e. crash accessing it).
What could be the reasons for that? I'm assuming user-error in our code, but I don't see why yet.

Thanks for any insights. --DD

pgsql-general by date:

Previous
From: Klaudie Willis
Date:
Subject: Re: When Update balloons memory
Next
From: Dmitry Igrishin
Date:
Subject: Re: LibPQ: Lifetime of PGresult passed in to PQnoticeReceiver callback