Databases in Console

The Databases section is used for day-to-day work with databases themselves: creation, state inspection, DSN retrieval, opening Monitoring, and deletion.

Creating a database

A database can be created either from the Databases section or directly from a tenant page.

Usually, you specify:

• name;
• size.

Database names should remain PostgreSQL-friendly: no spaces, no Cyrillic, using Latin letters / digits / _ / $.

What happens after creation

The SPG99 serverless model is important here:

• the database appears in the catalog and storage layer immediately;
• a permanently running writer does not have to start at that same moment;
• the first client connection through Gateway may wake the database up automatically.

That is why the stopped state after creation is normal and efficient behavior.

Database states

In Console, the user usually sees these states:

• Creating
• Booting
• Ready
• Stopping
• Stopped
• Deleting
• Error

The practical meaning is simple:

• Ready — you can work;
• Stopped — the first connection may trigger auto-start;
• transition states usually require only waiting;
• Error — a reason to open Monitoring.

The database card

The page of a specific database is one of the main working screens in Console. It usually shows:

• the database name and tenant;
• db id;
• the current state;
• size;
• the number of active connections;
• creation and update time;
• last-used time;
• worker_id, if the writer is active;
• warnings, if any.

In the new model, it is also useful to look at the runtime fields if they are shown in your UI build:

• current_profile
• target_profile
• scale_state
• freeze_new_checkouts
• scale_failure_reason

These fields help you understand whether the database is in normal operation, in cold start, or in a controlled handoff between writer profiles.

DSN and connection examples

One of the main advantages of Console is the ready-made connection string for the selected database. In the UI, you can usually:

• copy the DSN;
• get examples for common clients;
• download a .env, if that feature is enabled.

If the database is in stopped, the first connection may take a bit longer than subsequent ones. This is expected behavior in a serverless platform.

The global Databases list

When the number of databases grows, the Databases section is more convenient than opening each tenant separately. It usually provides:

• a global list of databases across the account;
• search by name;
• filtering by tenant;
• filtering by state;
• quick access to Monitoring and the database card.

After the autoscaler was introduced, it also became especially convenient for quickly finding databases that are not merely ready, but are currently in a runtime transition between profiles.