Re: pg_stat_statements requires compute_query_id

2021-05-10 Thread Pavel Stehule
po 10. 5. 2021 v 19:03 odesílatel Maciek Sakrejda napsal: > On Mon, May 10, 2021 at 7:43 AM Julien Rouhaud wrote: > > On Mon, May 10, 2021 at 04:36:16PM +0200, Pavel Stehule wrote: > > > I expected just an empty column query_id and workable extension. This > > > doesn't look well. > > > > > >

Re: pg_stat_statements requires compute_query_id

2021-05-10 Thread Maciek Sakrejda
On Mon, May 10, 2021 at 7:43 AM Julien Rouhaud wrote: > On Mon, May 10, 2021 at 04:36:16PM +0200, Pavel Stehule wrote: > > I expected just an empty column query_id and workable extension. This > > doesn't look well. > > > > More, it increases the (little bit) complexity of migration to Postgres

Re: pg_stat_statements requires compute_query_id

2021-05-10 Thread Julien Rouhaud
Hi Pavel, On Mon, May 10, 2021 at 04:36:16PM +0200, Pavel Stehule wrote: > > I tested features of Postgres 14. The extension pg_stat_statements didn't > work to me until I enabled compute_query_id. Is it expected behaviour? Yes. > I expected just an empty column query_id and workable

pg_stat_statements requires compute_query_id

2021-05-10 Thread Pavel Stehule
Hi I tested features of Postgres 14. The extension pg_stat_statements didn't work to me until I enabled compute_query_id. Is it expected behaviour? I expected just an empty column query_id and workable extension. This doesn't look well. More, it increases the (little bit) complexity of