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

Поиск
Список
Период
Сортировка
От Greg Sabino Mullane
Тема Re: Tracing libpq client: Only with PQtrace()?
Дата
Msg-id CAKAnmmKxUOcVk_NWVtxhRd_ks-MHKKt4hHU0Z+WTAkBEoLjC7w@mail.gmail.com
обсуждение исходный текст
Ответ на [MASSMAIL]Tracing libpq client: Only with PQtrace()?  (Sebastien Flaesch <sebastien.flaesch@4js.com>)
Ответы Re: Tracing libpq client: Only with PQtrace()?  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Re: Tracing libpq client: Only with PQtrace()?  (Sebastien Flaesch <sebastien.flaesch@4js.com>)
Список 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 по дате отправления:

Предыдущее
От: Sebastien Flaesch
Дата:
Сообщение: Re: prepared statement "cu1" already exists (but it does not)
Следующее
От: Thiemo Kellner
Дата:
Сообщение: [MASSMAIL][Code: 0, SQL State: 0A000] when "typing" from pg_catalog