Re: query_id, pg_stat_activity, extended query protocol

Поиск
Список
Период
Сортировка
От Anthonin Bonnefoy
Тема Re: query_id, pg_stat_activity, extended query protocol
Дата
Msg-id CAO6_XqqYLU0Qw1YkjdOM8ciJ9UsUGccRgQyNhR=R=YJuZkU5jA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: query_id, pg_stat_activity, extended query protocol  ("Imseih (AWS), Sami" <simseih@amazon.com>)
Ответы Re: query_id, pg_stat_activity, extended query protocol
Список pgsql-hackers
Hi,

Wouldn't it be enough to call pgstat_report_query_id in ExecutorRun
and ProcessUtility? With those changes [1], both normal statements and
utility statements called through extended protocol will correctly
report the query_id.

-- Test utility statement with extended protocol
show all \bind \g

-- Check reported query_id
select query, query_id from pg_stat_activity where
application_name ='psql' and pid!=pg_backend_pid();
   query   |      query_id
-----------+---------------------
 show all  | -866221123969716490

[1] https://github.com/bonnefoa/postgres/commit/bf4b332d7b481549c6d9cfa70db51e39a305b9b2

Regards,
Anthonin



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Nazir Bilal Yavuz
Дата:
Сообщение: Re: Use read streams in CREATE DATABASE command when the strategy is wal_log
Следующее
От: Matthias van de Meent
Дата:
Сообщение: Re: Expand applicability of aggregate's sortop optimization