Skip to content
This repository has been archived by the owner on Dec 17, 2024. It is now read-only.

[-] fix "invalid command 'BEGIN READ WRITE'" error when '--conn-pooling' option is on #586

Merged
merged 1 commit into from
Mar 6, 2023

Conversation

IlyaTsoi
Copy link
Contributor

If the gatherer is running with the '--conn-pooling on' option fetching pgbouncer metrics fails with errors "invalid command 'BEGIN READ WRITE'. Use SHOW HELP". This changes remove 'sqlLockTimeout' from 'sqlToExec' for pgbouncer metrics and assign usage 'DBExecRead' method for pgbouncer metrics independently of '--conn-pooling' option value

If the gatherer is running with the '--conn-pooling on' option, then fetching pgbouncer metrics fails with errors "invalid command 'BEGIN READ WRITE'. Use SHOW HELP". This changes remove 'sqlLockTimeout' from 'sqlToExec' for pgbouncer metrics and assign usage 'DBExecRead' for pgbouncer metrics independently of '--conn-pooling' option value
@IlyaTsoi
Copy link
Contributor Author

This error is reproduced when fetching postgres metrics via pgbouncer (in this case using --conn-pooling option is recomend).

@pashagolub pashagolub changed the title fix "invalid command 'BEGIN READ WRITE'" error when '--conn-pooling' option is on [-] fix "invalid command 'BEGIN READ WRITE'" error when '--conn-pooling' option is on Feb 9, 2023
@pashagolub pashagolub self-assigned this Mar 6, 2023
@pashagolub
Copy link
Collaborator

Thanks for the help!

@pashagolub pashagolub merged commit 105e439 into cybertec-postgresql:master Mar 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants