PostgreSQL Databases

Create PostgreSQL databases and give your applications access to them.

Where to find it: Open the account and choose PostgreSQL Databases.

Available to: The account owner, their reseller or the server administrator. Availability depends on the hosting plan and installed services.

What this page does

Use it to create in your account 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

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

1. Create the database within the account's allowed limit.
2. Create a strong, separate login role.
3. Grant only the required access to the selected database.
4. Save credentials in the application secret configuration, not in documentation.
5. Test application connectivity and run a backup.

Database users and privileges

Databases and login users are separate resources. Create the intended database and explicitly assign the users/privileges it needs. Where the form offers “Create a new user with the same name”, review that choice rather than assuming every database automatically has a separate login.

Use only the required privileges, verify the active database service/profile, and test the application connection after a password or grant change. MySQL and PostgreSQL have separate resource sets and limits; a database existing in one service does not make it available in the other. Deleting a database is different from removing one user’s access.

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.