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

Поиск
Список
Период
Сортировка
От Sebastien Flaesch
Тема Re: Tracing libpq client: Only with PQtrace()?
Дата
Msg-id AM9P191MB1286B884F6C9B0263A0FFEDDB0072@AM9P191MB1286.EURP191.PROD.OUTLOOK.COM
обсуждение исходный текст
Ответ на Re: Tracing libpq client: Only with PQtrace()?  (Greg Sabino Mullane <htamfids@gmail.com>)
Список pgsql-general
Yep I got it, thanks for the suggestion!
Seb

From: Greg Sabino Mullane <htamfids@gmail.com>
Sent: Tuesday, April 9, 2024 4:50 PM
To: Sebastien Flaesch <sebastien.flaesch@4js.com>
Cc: pgsql-general <pgsql-general@lists.postgresql.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.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 по дате отправления:

Предыдущее
От: Adrian Klaver
Дата:
Сообщение: Re: [Code: 0, SQL State: 0A000] when "typing" from pg_catalog
Следующее
От: Lok P
Дата:
Сообщение: [MASSMAIL]Issue with date/timezone conversion function