Skip to content
In this postPostgreSQL

Postgres 19 is stable on Layerbase

Start a new database on PostgreSQL 19.0 or upgrade your existing 19 beta database, including on the Free plan.

By Bob Bass2 min read
PostgreSQLDatabases

Postgres 19 is now the default for new PostgreSQL databases on Layerbase. We opened the beta in July, so some of you already have months of work on it. You can upgrade that database to 19.0 on your current plan, including Free.

If you already run the beta

Open your database in the Cloud dashboard, review the version update, and confirm the move to stable. Choose a time when your application can reconnect. Keep your existing connection string. Once the database is back, open a fresh connection and run:

sql
SHOW server_version;

You should see 19.0. We tested this on a disposable Free database on staging. We wrote 25 rows on 19beta3, upgraded through the owner API, and reconnected using the original connection string. All 25 rows matched their pre-upgrade checksum.

Start a project on stable

Create a PostgreSQL database and leave the default version selected. If you want to try a schema change before pointing your application at it, create a branch and run the migration against the branch's connection string. That gives you a copy of your data on which to check the result. Database branching guide

If your account has been around for a while, the create form may select 18.7 and label 19.0 as Update required. To create on 19.0, approve the update under Maintenance, which briefly restarts the databases on your account. Otherwise keep 18.7 and create the database right away.

For geospatial queries, PostgreSQL 19.0 includes core PostGIS 3.7.0. For embedding searches, enable pgvector under its SQL extension name, vector. Open the Extensions tab to see what is available and enabled on your database. PostgreSQL extensions

Bring an existing Postgres database

If your application already runs on Neon or Supabase, use the migration flow to import its PostgreSQL schema and data. Before switching your application, check any extensions it depends on, compare the tables and row counts, and test a representative query against the new connection. Plan the cutover around writes made after the import starts. Cloud migration guide

Support chat