You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Without any further information, I'd assume this is from the queries.yamlpg_stat_statements section, which still uses the "old" column names that were valid up to PostgreSQL 12. From PostgreSQL 13 onward, some of the column names need to be adjusted, they are now called "total_exec_time", "min_exec_time", etc.
Please also note that adding the pg_stat_statements section can (and on most database probably will) introduce very high cardinality because for each query pattern, there will be a corresponding set of metrics. If you are not 100% sure you need those metrics, you should probably drop the section from your user queries. There is even a pull request open to add a warning to the docs about this: #561
Also, as a side note, just using "bug" as a title and a single lien of output for the description is probably not the fastest way to get help or feedback from a project.
err="Error running query on database "ssssss:5432": pg_stat_statements pq: column "total_time" does not exist"
The text was updated successfully, but these errors were encountered: