Re: Tracing libpq client: Only with PQtrace()? - Mailing list pgsql-general

From Greg Sabino Mullane
Subject Re: Tracing libpq client: Only with PQtrace()?
Date
Msg-id CAKAnmmKxUOcVk_NWVtxhRd_ks-MHKKt4hHU0Z+WTAkBEoLjC7w@mail.gmail.com
Whole thread Raw
In response to [MASSMAIL]Tracing libpq client: Only with PQtrace()?  (Sebastien Flaesch <sebastien.flaesch@4js.com>)
Responses Re: Tracing libpq client: Only with PQtrace()?
Re: Tracing libpq client: Only with PQtrace()?
List pgsql-general
On Tue, Apr 9, 2024 at 8:51 AM Sebastien Flaesch <sebastien.flaesch@4js.com> wrote:
Is the PQtrace() API the only way to enable libpq client tracing?

I thought about some environment variable of client configuration setting...

That's generally the job of the client, or more specifically, the driver providing the interface between your program and the libpq API. Unless you are writing at the low level yourself, in which case, you would need to have your program detect an env and call PQtrace() as needed. 


Cheers,
Greg
 

pgsql-general by date:

Previous
From: Sebastien Flaesch
Date:
Subject: Re: prepared statement "cu1" already exists (but it does not)
Next
From: Thiemo Kellner
Date:
Subject: [MASSMAIL][Code: 0, SQL State: 0A000] when "typing" from pg_catalog