AlloyDB para PostgreSQL with DBine
How to connect DBine to AlloyDB para PostgreSQL and what you can do once it's connected. This page is written from what the AlloyDB para PostgreSQL driver says about itself, so it matches the version of DBine you download.
Connect
- In DBine, open New connection.
- Pick AlloyDB para PostgreSQL in the list of engines.
- Fill in the fields below, press Test connection and then Save.
Default port: 5432.
General
| Field | Description |
|---|---|
| Server required | The instance IP, or 127.0.0.1 if you use AlloyDB Auth Proxy. Example: localhost |
| Port | |
| Database | |
| Authentication | With AWS IAM, Google Cloud IAM or Entra ID, DBine requests a new token before each connection using this machine's credentials (aws, gcloud or az): no need to paste tokens that expire. They require TLS with a verified server certificate. The user is the database user (the IAM user, the account or the group). Options: Username and password, Google Cloud IAM Default: Username and password |
| Google Cloud account | Optional: the gcloud account that requests the token. Empty: the active one in gcloud (gcloud auth login), the application default credentials or the machine's service account. Example: ana@company.comOnly with Authentication: Google Cloud IAM. |
| User | |
| Password | Kept in the system keychain, never in DBine's files. Only with Authentication: Username and password. |
| Read-only | On or off. |
SSH tunnel. The connection can go through an SSH server, even through a chain of bastions, with a password, a private key or the SSH agent. The server's fingerprint is checked against known_hosts or confirmed the first time.
SSL/TLS
| Field | Description |
|---|---|
| Encrypt the connection (TLS) | On or off. |
| Trust the server certificate | On or off. |
| CA certificate (PEM) | To verify the server: the cluster CA (gcloud alloydb clusters describe). A file on this computer. |
Advanced
| Field | Description |
|---|---|
| Query protocol | Automatic uses the extended query protocol and falls back to the simple one if the server doesn't accept it. "Simple protocol only" is for gateways and proxies that reject the extended protocol. Options: Automatic, Simple protocol only Default: Automatic |
What the explorer shows
Under the connection: Databases, each with its schemas. Inside each one:
- Tables
- Views
- Materialized views
- Procedures
- Functions
- Triggers
- Sequences
- Types
Query editor
The editor uses SQL, with completion for the connection's objects. Statements and commands run against the database selected in the tab.
Ready-made templates for new objects:
- New view
- New materialized view
- New procedure
- New function
- New trigger
Tools for AlloyDB para PostgreSQL
Available
- Graphical execution plans
- Live query profiler
- Server monitor
- Sessions and running queries
- End a session
- Locks: who blocks whom
- Cancel another session's query from the sessions list
- Manual transactions (commit and rollback)
- Index usage
- Create databases
- Drop databases
- Database properties
- Relations in the ER diagram
- Visual designer for new objects
- Rename objects
- Compare and sync schemas
- Clone tables
- Native bulk load when migrating data
- Users and permissions
Not available for AlloyDB para PostgreSQL
- Backups
Why a tool doesn't apply to an engine, and the details of each one, are in the engine support reference.
Generated from the AlloyDB para PostgreSQL driver 0.1.18, which DBine downloads the first time you connect to AlloyDB para PostgreSQL.