Re: compute_query_id and pg_stat_statements

Поиск
Список
Период
Сортировка
От Julien Rouhaud
Тема Re: compute_query_id and pg_stat_statements
Дата
Msg-id 20210512061049.dykngnivdoesquxb@nol
обсуждение исходный текст
Ответ на Re: compute_query_id and pg_stat_statements  (Pavel Stehule <pavel.stehule@gmail.com>)
Ответы Re: compute_query_id and pg_stat_statements  (Pavel Stehule <pavel.stehule@gmail.com>)
Список pgsql-hackers
On Wed, May 12, 2021 at 07:49:13AM +0200, Pavel Stehule wrote:
> 
> > Ah, I missed that case.  And we are wanting to use pg_stat_statements
> > with (almost) zero-config?  How about the following behavior?
> >
> >
> Until now, the pg_stat_statements was zero-config. So the change is not
> user friendly.

Apart from configuring shared_preload_libraries, but agreed.

> The idea so pg_stat_statements requires enabled computed_query_id is not
> good. There should be dependency only on the queryid column.

I agree that requiring to change compute_query_id when you already added
pg_stat_statements in shared_preload_libraries isn't good, and the patch I sent
yesterday would fix that.



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

Предыдущее
От: Pavel Stehule
Дата:
Сообщение: Re: compute_query_id and pg_stat_statements
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: proposal: possibility to read dumped table's name from file