You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like there is a bug in PostgreSQL where passwords containing two or more consecutive $$ special characters are being converted into numbers when applied
#12059
Open
doyeon1001 opened this issue
Dec 9, 2024
· 0 comments
Describe the bug
It seems like there is a bug in PostgreSQL where passwords containing two or more consecutive $$ special characters are being converted into numbers when applied.
My postgresql password is $$Data18000658! but looking at the logs, it appears to be in numeric format.
I’ve tried using secrets and wrapping it with single quotes(also double quotes) , but the issue persists.
It's bug, right?
To Reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
kubernetes(AKS)
Datahub version : v0.14.1
Azure Database for PostgreSQL - Flexible Server
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
It seems like there is a bug in PostgreSQL where passwords containing two or more consecutive $$ special characters are being converted into numbers when applied.
My postgresql password is $$Data18000658! but looking at the logs, it appears to be in numeric format.
I’ve tried using secrets and wrapping it with single quotes(also double quotes) , but the issue persists.
It's bug, right?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: