Re: Tracing libpq client: Only with PQtrace()?

Yep I got it, thanks for the suggestion!
Seb
________________________________
From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
Sent: Tuesday, April 9, 2024 4:50 PM
To: Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com>
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Tracing libpq client: Only with PQtrace()?

EXTERNAL: Do not click links or open attachments if you do not recognize the sender.

On Tue, Apr 9, 2024 at 8:51 AM Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com<mailto:sebastien(dot)flaesch(at)4js(dot)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.

See for example https://metacpan.org/pod/DBD::Pg#parse_trace_flag-and-parse_trace_flags<https://urldefense.com/v3/__https://metacpan.org/pod/DBD::Pg*parse_trace_flag-and-parse_trace_flags__;Iw!!I_DbfM1H!CShCRGSMCXDnZkZhChWyuMkn2offRsd-E0IeowBRQDEXbGIcpIs0rTpnx_2a79rrfeQkcbMbt2QCBlKrmHtlFw$>

Cheers,
Greg