Skip to content

bug #579

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
notionev opened this issue Sep 22, 2021 · 1 comment
Open

bug #579

notionev opened this issue Sep 22, 2021 · 1 comment

Comments

@notionev
Copy link

err="Error running query on database "ssssss:5432": pg_stat_statements pq: column "total_time" does not exist"

@mbra
Copy link

mbra commented Oct 31, 2021

Without any further information, I'd assume this is from the queries.yaml pg_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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants