Database service admin
Run service maintenance, deploy or remove a service, and manage console-user access from the Database service admin tab.
Open a database service and select Database service admin at the right end of its tab row. The navigation on the left has Operations, Management, Users & roles and, for admins, Service access. Select a section to show its controls on the right.
Operators can run some maintenance actions here; others need an admin. An admin can also do everything an operator can do. See Roles for the full permission list.
Operations
This section opens by default. It has buttons to start maintenance work. To read the history and logs of that work, use the separate Operations tab in the service’s tab row.
These actions need a Running service with no other operation in progress. A disabled button gives the reason it is unavailable. The console can also refuse a request if the service is not ready for it.
Apply backup config
Operator or higher. Select Apply backup config to review the backup changes, then confirm. The console reapplies backup servers, schedules and retention to the servers. The action is unavailable if no backups are set up. Edit backup settings on the Backups tab.
Apply exporters config
Operator or higher. Select Apply exporters config to reinstall the exporters and their scrape configuration on the servers. Use the Monitoring tab to check the resulting metrics.
Retune TimescaleDB
Admin only. Select Retune to tune PostgreSQL for the license size, or the server size if the server is smaller. Read the confirmation before continuing: retuning restarts the database.
On HA, replicas restart one at a time, then the primary switches over to a replica and restarts. Writes stop for a few seconds and open transactions on the old primary end. A single-node service is unavailable until its restart finishes. See Licensing.
Change VIP
Admin only. This row appears for an HA service that has a virtual IP. Select Change VIP and follow Change the VIP. HAProxy and keepalived restart on one node at a time. Clients using the old address disconnect when it changes, so plan the client address change too.
Rolling restart
Operator or higher. Select Rolling restart and confirm to restart PostgreSQL on each node, one at a time. The primary restarts in place: its connections drop briefly. This action does not use the switchover sequence of Retune TimescaleDB. On a single-node service, the restart interrupts all database connections.
Management
Select Management on the left. Each row describes the action and has its button on the right. Check both the action and the service status before confirming.
| Action | Required role | Available statuses |
|---|---|---|
| Deploy | Operator or higher | Pending, Removed, Failed or Running |
| Remove from servers | Admin | Running or Failed |
| Delete from console | Admin | Pending, Removed or Failed |
Wait for any operation in progress to finish before starting a management action.
Deploy
Select Deploy to install and configure the service on its assigned servers. You can also redeploy a Running service from this section to apply its configuration again. Follow the run on the Operations tab.
Remove from servers
The console also removes the service’s software and OS settings, and the VIP leaves the servers. Backups and the service’s saved settings stay, so you can deploy it again. A separate DCS cluster and backup server stay.
If a server cannot be cleaned, it shows Needs cleanup. Read the removal log, then follow Server cleanup before reusing that server.
Delete from console
Select Delete to remove the service record from the console. This does not clean its servers. If the service has been deployed, use Remove from servers first. A Failed status allows Delete, but does not prove that the servers are already clean.
Users & roles
This section concerns PostgreSQL users inside the database. The console does not yet list or manage those users here. The password command shown in the section is a helper to run through a database connection, not an editable user form.
Manage database roles through a PostgreSQL client, or use the SQL browser if you have the console admin role. See Connect for connection details.
For accounts used to log in to the console, use Administration → Users & roles instead.
Service access
Admin only. Select Service access on the left to see which console users have access to this service. These are console permissions, separate from PostgreSQL roles and database connection credentials.
The table shows each user’s Default role, any service-specific Grant, and the resulting Role on this service. The resulting role is the higher of the default role and the grant. Disabled users can still appear in the table.
To give access:
- Select Add grant above the table, on the right.
- In the side panel, select a User and a Role: Viewer or Operator.
- Select Add grant at the bottom of the panel.
A grant applies at once, including to open sessions. It cannot give the admin role or reduce a user’s default role. For example, an Operator grant lets a default Viewer operate this service without changing their role on other services.
To remove a grant, open the three-dot menu at the right end of the user’s row and select Remove grant. Their default role still applies; removing a grant does not revoke access that the default role already provides.
For changing an existing grant or restricting a user to selected services, see Service access.