pg_stat_statements requires compute_query_id - Mailing list pgsql-hackers

From Pavel Stehule
Subject pg_stat_statements requires compute_query_id
Date
Msg-id CAFj8pRCKqpi_PTCYFYRbSX_bo8CxppXbwjZEyP9ADUyfqrfQPw@mail.gmail.com
Whole thread Raw
Responses Re: pg_stat_statements requires compute_query_id
List pgsql-hackers
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 migration to Postgres 14.

Regards

Pavel


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: GetSubscriptionRelations declares too many scan keys
Next
From: Justin Pryzby
Date:
Subject: Re: PG 14 release notes, first draft