Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)
Дата
Msg-id 14734.1331668365@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)  (Peter Geoghegan <peter@2ndquadrant.com>)
Ответы Re: Re: pg_stat_statements normalisation without invasive changes to the parser (was: Next steps on pg_stat_statements normalisation)
Список pgsql-hackers
Peter Geoghegan <peter@2ndquadrant.com> writes:
> I probably should have exposed the query_id directly in the
> pg_stat_statements view, perhaps as "query_hash".

FWIW, I think that's a pretty bad idea; the hash seems to me to be
strictly an internal matter.  Given the sponginess of its definition
I don't really want it exposed to users.
        regards, tom lane


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

Предыдущее
От: "Kevin Grittner"
Дата:
Сообщение: Re: pg_upgrade and statistics
Следующее
От: Dimitri Fontaine
Дата:
Сообщение: Re: Command Triggers, patch v11