Accessing the Settings

1. In the sidebar menu, click Projects
2. Find and click the desired database project name
3. On the project page, click the "Edit" button in the top-right corner

Available Settings

Project Name

The project name can be changed at any time.

Rules:

• Minimum: 6 characters
• Maximum: 32 characters
• Only lowercase letters, numbers, and hyphens

Note: Changing the name does not affect the existing subdomain.

Project Description

The project description can be changed at any time.

Characteristics:

• Optional field to describe the project purpose
• Helps identify and organize your projects
• Can include information such as environment, customer, or purpose

Database Password

You can change the PostgreSQL administrator password at any time.

How to change it:

1. In the password section, enter the new password
2. Click Save

Important: After changing the password, update the password in your application that uses this database.

PostgreSQL Version

The PostgreSQL version can be updated.

Available versions:

• PostgreSQL 15
• PostgreSQL 16
• PostgreSQL 17
• PostgreSQL 18

How to update:

1. Select the desired new version
2. Click Save

Warning: Version upgrades can cause brief periods of downtime. We recommend making the change during low-traffic hours.

Important: PostgreSQL version downgrade is not supported.

Connection String

The connection string is generated automatically and can be viewed at any time.

Format:

postgres://usuario:senha@host:porta/nome_banco

To copy: Click the copy button next to the connection string.

Tip: Use this string in your application's DATABASE_URL environment variable to connect to the database.

Scalability (Instances)

You can increase or decrease the total number of database instances.

Limits:

• Minimum: 1 instance
• Maximum: 3 instances

Impact:

• More instances = higher availability
• More instances = higher cost
• Additional instances offer automatic failover
• Secondary instances can be used as read-only, reducing load on the primary instance

Note: For projects with more than 1 instance, automatic failover is enabled. If the primary instance fails, a secondary instance takes over automatically.

Storage

Database storage can be adjusted.

Limits:

• Minimum: 1 GB
• Maximum: 250 GB

Impact:

• For hourly projects: storage can be increased
• For monthly/yearly contracts: storage can only be increased at the time of project creation, or after the contract ends

Warning: Storage reduction is not supported. Make sure to allocate enough space for your data.

Project Actions

Stop the Project

When you stop the project:

• The database is stopped with a graceful 30-second shutdown, allowing current queries to finish
• Database instances are shut down
• The project becomes inaccessible
• For hourly projects, plan billing stops, but storage costs continue

When to use it:

• When you do not need the database temporarily
• To save costs on hourly projects

Start the Project

To start a stopped project:

• The database starts again
• Database instances are initialized
• The project becomes accessible again
• For hourly projects, billing resumes

Delete the Project

Deletion is permanent and irreversible.

What happens:

• All database instances are removed
• All data is deleted

Requirements:

• For hourly projects, the instance can be deleted at any time
• For contracts, wait until expiration and disable automatic renewal

Warning: Back up your data with pg_dump before deleting. This action cannot be undone.

Next Steps

• Create a PostgreSQL Database
• Project Metrics and Insights
• Payment Settings

FAQ

Can I change the database password?

Yes. At any time through the project settings. Remember to update the password in your application after changing it in the database.

Does changing settings cause downtime?

It depends on the change:

• Password: Does not cause downtime
• PostgreSQL version: May cause brief downtime
• Instances: Instances are restarted
• Storage: Does not cause downtime (only for increases on contracts)

Can I restore a deleted database?

No. Deletion is permanent. Data cannot be recovered. Make sure to back it up before deleting.

What happens if the primary instance fails?

For projects with more than 1 instance, automatic failover occurs:

• A secondary instance becomes the primary
• A new secondary instance is created automatically
• Your application continues working without manual intervention

How do I back up my database?

You can export data using tools such as pg_dump or by connecting directly to the database and exporting the required data.

Can I connect external applications to the database?

Yes. Use the connection string provided in the settings. Database projects do not provide whitelist or blacklist controls, so restrict access at the application, client network, or credential-management layer when needed.