Saving connection fails when using .pgpass (empty password) even though test connection succeeds #60
Description
Description
When using pgStudio with PostgreSQL authentication via .pgpass, the Test Connection succeeds, but saving / adding the connection fails with:
Failed to connect: empty password returned by client
This occurs even though:
The same .pgpass entry works with psql and other clients (e.g., DBeaver)
pgStudio’s Test Connection succeeds using the same parameters
It appears that pgStudio reads .pgpass during connection testing, but does not support persisting a connection that relies solely on .pgpass, resulting in an empty password being saved.
Steps to Reproduce
- Configure a valid ~/.pgpass entry for a PostgreSQL database
- Open pgStudio
- Add a new connection without entering a password
- Click Test Connection → ✅ succeeds
- Click Add / Save Connection
- Attempt to connect using the saved connection
Expected Behavior
A connection that successfully authenticates via .pgpass during testing should be saveable and reconnect successfully
Or, documentation should clearly state that .pgpass is not supported for persisted connections
Actual Behavior
Saving the connection fails or results in:
Failed to connect: empty password returned by client
The connection cannot be reused unless a password is explicitly stored
Notes
There does not appear to be documented support for .pgpass, PGPASSFILE, or passfile in pgStudio connection configuration
This makes .pgpass usable only for ad‑hoc/test connections, not saved ones
Environment
pgStudio extension (dev-asterix)
PostgreSQL (libpq-based authentication)
OS: macOS / Linux (same behavior)