Re: compute_query_id and pg_stat_statements

Поиск
Список
Период
Сортировка
От Andrew Dunstan
Тема Re: compute_query_id and pg_stat_statements
Дата
Msg-id 39709c58-34fc-942c-d0f9-aec54964a3d7@dunslane.net
обсуждение исходный текст
Ответ на Re: compute_query_id and pg_stat_statements  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Ответы Re: compute_query_id and pg_stat_statements  (Bruce Momjian <bruce@momjian.us>)
Re: compute_query_id and pg_stat_statements  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers
On 5/13/21 3:04 PM, Alvaro Herrera wrote:
> On 2021-May-13, Stephen Frost wrote:
>
>> Or just accept that this is a bit hokey with the 'auto' approach.  I get
>> Bruce has concerns about it but I'm not convinced that it's actually all
>> that bad to go with that.
> Yeah, I think the alleged confusion there is overstated.
>
> I'm happy to act as committer for that if he wants to step away from it.
> I'm already used to being lapidated at every corner anyway.
>


Many thanks Alvaro, among other things for teaching me a new word.


cheers


(delapidated) andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com




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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: OOM in spgist insert
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Condition pushdown: why (=) is pushed down into join, but BETWEEN or >= is not?