Feedback-ID: ia2694551:Fastmail
Date: Tue, 9 Apr 2024 17:01:22 +0200
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Greg Sabino Mullane <htamfids@gmail.com>
Cc: Sebastien Flaesch <sebastien.flaesch@4js.com>, 
	pgsql-general <pgsql-general@lists.postgresql.org>
Subject: Re: Tracing libpq client: Only with PQtrace()?
Message-ID: <202404091501.e4buwthhrd27@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAKAnmmKxUOcVk_NWVtxhRd_ks-MHKKt4hHU0Z+WTAkBEoLjC7w@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/202404091501.e4buwthhrd27%40alvherre.pgsql>
Precedence: bulk

On 2024-Apr-09, Greg Sabino Mullane wrote:

> 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.
> 
> See for example
> https://metacpan.org/pod/DBD::Pg#parse_trace_flag-and-parse_trace_flags

Another approach might be to use Wireshark, which has a decoder for the
Postgres FE/BE protocol.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"Pido que me den el Nobel por razones humanitarias" (Nicanor Parra)