Re: compute_query_id and pg_stat_statements
От | Maciek Sakrejda |
---|---|
Тема | Re: compute_query_id and pg_stat_statements |
Дата | |
Msg-id | CAOtHd0AzTxnoLHZXRQZo5jiyU5Rdya6OB1Z1EabhehMecpDzbA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: compute_query_id and pg_stat_statements (Julien Rouhaud <rjuju123@gmail.com>) |
Ответы |
Re: compute_query_id and pg_stat_statements
|
Список | pgsql-hackers |
On Wed, May 12, 2021 at 9:58 PM Julien Rouhaud <rjuju123@gmail.com> wrote: > Le jeu. 13 mai 2021 à 12:52, Maciek Sakrejda <m.sakrejda@gmail.com> a écrit : >> >> For what it's worth, I don't think the actual changing of an extra >> setting is that big a burden: it's the figuring out that you need to >> change it, and how you should configure it, that is the problem. >> Especially since all major search engines still seem to return 9.4 (!) >> documentation as the first hit for a "pg_stat_statements" search. The >> common case (installing pg_stat_statements but not tweaking query id >> generation) should be simple. > > > the v2 patch I sent should address both your requirements. Yes, thanks--I just tried it and this is great. I just wanted to argue against reversing course here.
В списке pgsql-hackers по дате отправления: