Re: compute_query_id and pg_stat_statements

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: compute_query_id and pg_stat_statements
Дата
Msg-id e832ac41-00dd-3a05-7f52-4b2ae4613508@enterprisedb.com
обсуждение исходный текст
Ответ на Re: compute_query_id and pg_stat_statements  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: compute_query_id and pg_stat_statements
Список pgsql-hackers
On 24.04.21 19:43, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
>> That's a pretty weird API.  I think we just need people to turn it on
>> like they are doing when the configure pg_stat_statements anyway.
>> pg_stat_statements already requires configuration anyway.
> 
> Agreed.  If pg_stat_statements were zero-configuration today then
> this would be an annoying new burden, but it isn't.

I think people can understand "add pg_stat_statements to 
shared_preload_libraries" and "install the extension".  You have to turn 
it on somehow after all.

Now there is the additional burden of turning on this weird setting that 
no one understands.  That's a 50% increase in burden.

And almost no one will want to use a nondefault setting.

pg_stat_statements is pretty popular.  I think leaving in this 
requirement will lead to widespread confusion and complaints.



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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Enhanced error message to include hint messages for redundant options error
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Does rewriteTargetListIU still need to add UPDATE tlist entries?