We are excited to announce the support of PostgreSQL 18.
PostgreSQL 18 improves performance for workloads of all sizes through a new I/O subsystem that has demonstrated up to 3× performance improvements when reading from storage, and also increases the number of queries that can use indexes. This release makes major-version upgrades less disruptive, accelerating upgrade times and reducing the time required to reach expected performance after an upgrade completes. Developers also benefit from PostgreSQL 18 features, including virtual generated columns that compute values at query time, and the database-friendly uuidv7() function that provides better indexing and read performance for UUIDs. PostgreSQL 18 makes it easier to integrate with single-sign on (SSO) systems with support for OAuth 2.0 authentication.
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 18, you would run:
gigalixir pg:upgrade -d $DATABASE_ID POSTGRES_18
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_18 | 2030-12-28 | 2034-01-01 |
| 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.