Closed bheemvennapureddy closed 3 weeks ago
If you want to mask the password, you should use PGPASSWORD env var like you would for psql, and exclude it from your connection string. This also ensures your command history doesn't log thr password.
This is the same behavior as psql and any libpq-based tool, https://www.postgresql.org/docs/current/libpq-envars.html
that works
I run into hba conf issues without passing the password in the connection string any insights you can share ?
I recommend debugging via psql and then emulating that in pg-schema-diff. If you find a discrepancy between the two, let me know. Not to sure exactly what is causing your issue.
I had to export export PGSSLMODE=require
as well for that.
mask password in the plan log when logging to the console.