-
Notifications
You must be signed in to change notification settings - Fork 261
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
pg_stat_all_tables info not reliable (or direct execute problem). #92
Comments
It happened only for a single dn so far, but from any coordinator. |
And bouncing DB does not help. |
@yazun I try to reproduce this promble, but it hasn't happend yet. I want to confirm some questions: |
@yazun |
Rescuing a very old thread just because I landed here in search for answers, I had a very similar issue and I got the erratic results resolved by means of issuing an |
We rely on updating stats on the coordinators on a global view by comparing pg_stat_all_tables differences between datanode and coordinator.
Noticing however very worrisome, erratic behaviour of the pg_stat_all_tables values.
Below you can see that values returned are either ok or nulls - they query is executed in second intervals and seem randomy returning proper values or nothing. This basically breaks coordinators update (
analyze(coordinator
).Do you have any idea why that could be happening? - Seems like a caching problem of some stale pool connection maybe?
How to fix it?
Thanks
The text was updated successfully, but these errors were encountered: