We are excited to announce the support of PostgreSQL 17.

PostgreSQL 17 delivers powerful performance boosts across the board. With up to 20x less memory used for the vacuum process, more resources are available for your applications. High-concurrency systems can see double the write speed, and faster scanning and analysis improve data operations overall. Query performance is also enhanced with quicker indexing and optimized planning, making PostgreSQL 17 a strong choice for demanding workloads.

Upgrading an existing database

Upgrade Concerns

Consult our full documentation for considerations and best practices when upgrading your database. It is important to consider feature compatibility, extension compatibility, and estimated downtimes before proceeding.

Performing the Upgrade

Upgrading to a newer PostgreSQL version is a straightforward process that will help you stay current with security updates and new features.

First, ensure you are using CLI 1.13.1 or greater.

gigalixir version

If you need help upgrading your CLI, follow our upgrade instructions.

When you are ready to perform the upgrade, identify your database ID with this command:

gigalixir pg

Once you have the database ID, run the following command to initiate the upgrade:

gigalixir pg:upgrade -d $DATABASE_ID VERSION

For example, to upgrade to PostgreSQL 17, you would run:

gigalixir pg:upgrade -d $DATABASE_ID POSTGRES_17

Note: If you’re using a version older than PostgreSQL 13, you’ll need to upgrade to version 13 before upgrading further.

Database End-of-life Schedule

Version	Extended Support	End-of-life
POSTGRES_17	2029-12-28	2033-01-01
POSTGRES_16	2028-12-28	2032-01-01
POSTGRES_15	2027-12-28	2031-01-01
POSTGRES_14	2026-12-28	2030-01-01
POSTGRES_13	2025-12-28	2029-01-01
POSTGRES_12	2024-12-28	2028-01-01
POSTGRES_11	2024-12-28	2028-01-01
POSTGRES_10	2024-12-28	2028-01-01
POSTGRES_9_6	2024-12-28	2028-01-01

More Information

For more information, please consult the Standard Tier Database Documentation.