-
Notifications
You must be signed in to change notification settings - Fork 176
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
check_postgresql_sequence exits with error when checking multiple databases #155
Comments
Hi @tomascassidy — which version of check_postgres? |
Also, I suspect this has more to do with how it's handling databases without sequences rather than something inherent to the versions specifically. Can you test creating a sequence in each of those databases and see if it then works? (Obviously this is something that would still need to be handled, but it would help narrow this down.) |
Hi @machack666 I am running the latest version 2.24.0-3.pgdg90+1 from the apt.postgresql.org repository. I created a new sequence in both the I then ran the same command again: Unfortunately the same error appears again. |
Hi, the error is due to the fact that if more than one database is found in the loop, the DB version can no longer be checked because it only exists in $db for the first database ($info->{db}[0]{version}). Workaround: For example you just need to change the following two lines
Then we use the "correct" SQL query for the sequences in PostgreSQL >= 10 and fill the corresponding variables. |
this workaround is no longer working.
|
Running the check_postgresql
sequence
action exits with an error when checking multiple databases.PostgreSQL 11.1
PostgreSQL 9.6
The text was updated successfully, but these errors were encountered: