Postgres compatibility

Neon is Postgres. However, as a managed Postgres service, there are some differences you should be aware of.

Postgres versions

Neon supports Postgres 14, 15, 16, 17. You can select the Postgres version you want to use when creating a Neon project. Postgres 16 is selected by default. For information about creating a Neon project, See Manage projects. Minor Postgres point releases are rolled out by Neon after extensive validation as part of regular platform maintenance.

Postgres extensions

Neon supports numerous Postgres extensions, and we regularly add support for more. For the extensions that Neon supports, see Postgres Extensions. To request support for additional extensions, please reach out to us on our Discord Server. Please keep in mind that privilege requirements, local file system access, and functionality that is incompatible with Neon features such as Autoscaling and Autosuspend may prevent Neon from being able to offer support for certain extensions.

Roles and permissions

Neon is a managed Postgres service, so you cannot access the host operating system, and you can't connect using the Postgres superuser account. In place of the Postgres superuser role, Neon provides a neon_superuser role.

Roles created in the Neon Console, CLI, or API, including the default role created with a Neon project, are granted membership in the neon_superuser role. For information about the privileges associated with this role, see The neon_superuser role.

Roles created in Neon with SQL syntax, from a command-line tool like psql or the Neon SQL Editor, have the same privileges as newly created roles in a standalone Postgres installation. These roles are not granted membership in the neon_superuser role. You must grant these roles the privileges you want them to have. For more information, see Manage roles with SQL.

Neon roles cannot install Postgres extensions other than those supported by Neon.

Postgres parameter settings

The following table shows parameter settings that are set explicitly for your Neon Postgres instance. These values may differ from standard Postgres defaults, and a few settings differ based on your Neon compute size.

Parameter settings that differ by compute size

Of the parameter settings listed above, the maintenance_work_mem, max_connections, and max_worker_processes differ by compute size, which is defined in Compute Units (CU). The following table shows values for each compute size.

Configuring Postgres parameters for a session, database, or role

Neon permits configuring parameters that have a user context, meaning that these parameters can be set for a session, database, or role. You can identify Postgres parameters with a user context by running the following query:

SELECT name
FROM pg_settings
WHERE context = 'user';

To set a parameter for a specific session, use a SET command.

For example, the maintenance_work_mem parameter supports a user context, which lets you set it for the current session with a SET command:

SET maintenance_work_mem='1 GB';

To set parameters for a database or role:

ALTER DATABASE neondb SET maintenance_work_mem='1 GB';

ALTER USER neondb_owner SET maintenance_work_mem='1 GB';

Postgres server logs

Currently, Postgres server logs can only be accessed Neon Support team. Should you require information from the Postgres server logs for troubleshooting purposes, please contact Neon Support.

Unlogged tables

Unlogged tables are maintained on Neon compute local storage. These tables do not survive compute restarts (including when a Neon compute is placed into an Idle state after a period of inactivity). This is unlike a standalone Postgres installation, where unlogged tables are only truncated in the event of abnormal process termination. Additionally, unlogged tables are limited by compute local storage size.

Memory

SQL queries and index builds can generate large volumes of data that may not fit in memory. In Neon, the size of your compute determines the amount of memory that is available. For information about compute size and available memory, see How to size your compute.

Temporary tables

Temporary tables, which are stored in compute local storage, are limited by compute local storage size.

Session context

The Neon cloud service automatically closes idle connections after a period of inactivity, as described in Compute lifecycle. When connections are closed, anything that exists within a session context is forgotten and must be recreated before being used again. For example, parameters set for a specific session, in-memory statistics, temporary tables, prepared statements, advisory locks, and notifications and listeners defined using NOTIFY/LISTEN commands only exist for the duration of the current session and are lost when the session ends. To avoid losing session-level contexts in Neon, you can disable Neon's autosuspend feature, which is possible on any of Neon's paid plans. However, disabling autosuspend also means that your compute will run 24/7. You can't disable autosuspend on Neon's Free plan, where your compute always autosuspends after 5 minutes of inactivity.

Statistics collection

Statistics collected by the Postgres cumulative statistics system are not saved when a Neon compute (where Postgres runs) is suspended due to inactivity or restarted. For information about the lifecycle of a Neon compute, see Compute lifecycle. For information about configuring Neon's autosuspend behavior, see Autosuspend.

Database encoding

Neon supports UTF8 encoding (Unicode, 8-bit variable-width encoding). This is the most widely used and recommended encoding for Postgres.

To view the encoding and collation for your database, you can run the following query:

SELECT
    pg_database.datname AS database_name,
    pg_encoding_to_char(pg_database.encoding) AS encoding,
    pg_database.datcollate AS collation,
    pg_database.datctype AS ctype
FROM
    pg_database
WHERE
    pg_database.datname = 'your_database_name';

You can also issue this command from psql or the Neon SQL Editor:

\l

Collation support

A collation is an SQL schema object that maps an SQL name to locales provided by libraries installed in the operating system. A collation has a provider that specifies which library supplies the locale data. A common standard provider, libc, uses locales provided by the operating system C library. By default, Neon uses the C collation provided by libc, which offers a simple binary sorting order based on the byte values of characters.

The C.UTF-8 collation is also available. While the C collation is strictly binary and limited to ASCII characters, C.UTF-8 supports the full range of UTF-8 encoded characters. To create a database with that collation, you can use the following syntax:

CREATE DATABASE my_database
ENCODING 'UTF8'
LC_COLLATE 'C.UTF-8'
LC_CTYPE 'C.UTF-8'
template template0;

Another provider supported by Neon is icu, which uses the external ICU library. In Neon, support for standard libc locales is limited compared to what you might find in a locally installed Postgres instance where there's typically a wider range of locales provided by libraries installed on your operating system. For this reason, Neon provides a full series of predefined icu locales in case you require locale-specific sorting or case conversions.

To view all of the predefined locales available to you, use the query SELECT * FROM pg_collation, or the command \dOS+ from the Neon SQL Editor or an SQL client like psql.

To create a database with a predefined icu locale, you can issue a query similar to this one with your preferred locale:

CREATE DATABASE my_arabic_db
LOCALE_PROVIDER icu
icu_locale 'ar-x-icu'
template template0;

To specify the locale for individual columns, you can use this syntax:

CREATE TABLE my_ru_table (
    id serial PRIMARY KEY,
    russian_text_column text COLLATE "ru-x-icu",
    description text
);

ICU also supports creating custom collations. For more information, see ICU Custom Collations.

For more about collations in Postgres, see Collation Support.

Event triggers

Postgres event triggers, which require Postgres superuser privileges, are currently not supported. Unlike regular triggers, which are attached to a single table and capture only DML events, event triggers are global to a particular database and are capable of capturing DDL events.

Attempting to create an event trigger will produce errors similar to these:

ERROR: permission denied to create event trigger "your_trigger_name" (SQLSTATE 42501)

ERROR:  permission denied to create event trigger "your_trigger_name"
HINT:  Must be superuser to create an event trigger.

Foreign Data Wrappers

Neon does not yet support Foreign Data Wrappers (FDW) or Postgres extensions such as postgres_fdw that provide this functionality. We intend to offer FDW support in a future release.

PostgreSQL documentation

Neon provides a mirror of the official PostgreSQL documentation on the Neon documentation site for the convenience of our users. As Neon is built on standard PostgreSQL, most information from the official PostgreSQL documentation applies to our platform. However, there are a few key differences to consider when referencing the official PostgreSQL docs:

• As a managed Postgres service, certain aspects of the official PostgreSQL documentation like installation procedures do not apply to Neon.
• Some features detailed in the official PostgreSQL documentation may not be relevant for Neon, such as those mentioned on this Postgres compatibility page.
• Features requiring the PostgreSQL superuser privilege may not be supported. See Roles and permissions above.
• Neon may not support all of the extensions mentioned in the official PostgreSQL documentation. See Postgres extensions above.