Fix HammerDB/PostgreSQL: use hex password to avoid TCL parsing error#686
Merged
Conversation
AlexW-F
force-pushed
the
users/alexwill/fix-hammerdb-password
branch
from
6a820b3 to
f2283b8
Compare
Contributor
|
Don't forget to up the version. |
AlexW-F
force-pushed
the
users/alexwill/fix-hammerdb-password
branch
from
f2283b8 to
c098f83
Compare
nchapagain001
approved these changes
Apr 11, 2026
AlexW-F
force-pushed
the
users/alexwill/fix-hammerdb-password
branch
from
c098f83 to
29dae0b
Compare
Base64 password contains + and = characters which break HammerDB 4.12's TCL diset command argument parsing. Changed to hex encoding which produces alphanumeric-only output across all three components that share the SuperUserPassword: - HammerDBExecutor - PostgreSQLServerConfiguration - SysbenchExecutor All three must use the same encoding since they share the same PostgreSQL credential. This has been the sole cause of HammerDB parse failures since Mar 16 (~1700 errors/day). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
AlexW-F
force-pushed
the
users/alexwill/fix-hammerdb-password
branch
from
29dae0b to
ea8aeab
Compare
nchapagain001
approved these changes
Apr 11, 2026
rudraptpsingh
pushed a commit
to rudraptpsingh/VirtualClient
that referenced
this pull request
May 26, 2026
…icrosoft#686) Base64 password contains + and = characters which break HammerDB 4.12's TCL diset command argument parsing. Changed to hex encoding which produces alphanumeric-only output across all three components that share the SuperUserPassword: - HammerDBExecutor - PostgreSQLServerConfiguration - SysbenchExecutor All three must use the same encoding since they share the same PostgreSQL credential. This has been the sole cause of HammerDB parse failures since Mar 16 (~1700 errors/day). Co-authored-by: Alex Williams-Ferreira <alexwill@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Base64 password contains + and = characters which break HammerDB 4.12's TCL diset command argument parsing. Changed to hex encoding which produces alphanumeric-only output across all three components that share the SuperUserPassword:
All three must use the same encoding since they share the same PostgreSQL credential.
This has been the sole cause of HammerDB parse failures since Mar 16 (~1700 errors/day).