Re: compute_query_id and pg_stat_statements
| От | Julien Rouhaud |
|---|---|
| Тема | Re: compute_query_id and pg_stat_statements |
| Дата | |
| Msg-id | 20210514142749.gaa26fk2txh7pwtx@nol обсуждение исходный текст |
| Ответ на | Re: compute_query_id and pg_stat_statements (Bruce Momjian <bruce@momjian.us>) |
| Список | pgsql-hackers |
On Fri, May 14, 2021 at 08:57:41AM -0400, Bruce Momjian wrote: > On Fri, May 14, 2021 at 08:35:14AM -0400, Bruce Momjian wrote: > > On Thu, May 13, 2021 at 09:41:42PM -0400, Bruce Momjian wrote: > > > I think if we keep the output as 'auto', and document that you check > > > pg_stat_activity for a hash to see if it is enabled, that gets us pretty > > > far. > > > > I think keeping the output as 'auto', and documenting that this query > > must be run to determine if the query id is being computed: > > > > SELECT query_id > > FROM pg_stat_activity > > WHERE pid = pg_backend_pid(); > > > > is the right approach. > > Actually, we talked about huge_pages = try needing to use OS commands to > see if huge pages are being used, so requiring an SQL query to see if > query id is being computed seems reasonable. I totally agree.
В списке pgsql-hackers по дате отправления: