PostgreSQL Databases
PostgreSQL Databases is the account workspace for databases, login roles, grants, and conditional pgAdmin access, all kept inside the selected hosting account boundary.
Where to find it: Open the account and choose PostgreSQL Databases.
Available to: The account user for their own account, plus root or the owning reseller when working inside that account. The item may be hidden when its feature profile or required service is disabled.
What this page does
Use it to create account-owned databases and roles, rotate role passwords, assign the required database access, review sizes or current assignments, and open the account pgAdmin workflow when the service is available.
Before you start
PostgreSQL must be enabled in Services and the account feature profile must allow the module. Plan database and role names, use one role per application where practical, generate strong credentials, and take a current backup before removing access or data.
Resource model
| Resource | Purpose |
|---|---|
| Database | The account-owned PostgreSQL data container used by an application. |
| Login role | The credential-bearing PostgreSQL identity used by an application or authorized operator. |
| Grant / privilege template | The allowed relationship between a role and selected account databases. |
| pgAdmin | A conditional browser administration handoff for the account's authorized PostgreSQL scope. |
Least privilege
Grant a role only the databases and privileges its application needs. Separate roles make credential rotation and incident containment easier. Removing a role or grant can stop a live application immediately, so find the application configuration before changing access.
Processes and backups
Use Account PgSQL Processes to investigate active account sessions and the PostgreSQL backup pages made available by the provider for recovery. Process termination is an incident action, not routine database housekeeping.
How to use it
- Create the database within the account's allowed limit.
- Create a strong, separate login role.
- Grant only the required access to the selected database.
- Save credentials in the application secret configuration, not in documentation.
- Test application connectivity and run a backup.
Result and next check
The account owns the database and role, the intended grant is visible, and the application connects without broader PostgreSQL access. A browser pgAdmin launch, when available, remains limited by the prepared account context.
Theme color