-
-
Notifications
You must be signed in to change notification settings - Fork 119
PgPass host still not correctly matched #365
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
What happened?
This is a follow-up from #356.
Steps to reproduce
- in Edit Connection dialog, enable Use ~/.pgpass
- notice the green message
~/.pgpass found – matching entry exists - click Save
- open the same connection
- Use ~/.pgpass is disabled -> this setting isn't persisted
- click Test connection
- error message
connection to server at "MYHOST.postgres.database.azure.com" (4.251.RED.ACT), port 5432 failed: FATAL: no pg_hba.conf entry for host "185.10.RED.ACT", user "PostgresAdmins", database "ed", no encryption
Expected behavior
- the Use ~/.pgpass setting should be saved
- connecting to the DB should use the same logic as the green check when the setting is activated
Database type
PostgreSQL
TablePro version
0.20.2
macOS version & chip
No response
Screenshots / Logs
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working