EDB Postgres Extended Server 13 release notes v13

Suggest edits

2ndQuadrant Postgres 13.23

Release date: 2025-11-13

This release is primarily an upstream merge.

Changes

Merged with community PostgreSQL 13.23. See the PostgreSQL 13.23 Release Notes for more information.

2ndQuadrant Postgres 13.22

Release date: 2025-08-14

This release is primarily an upstream merge.

Changes

Merged with community PostgreSQL 13.22. See the PostgreSQL 13.22 Release Notes for more information.

It also includes a security fix that was incorporated in 13.22: CVE-2025-8713, CVE-2025-8714 and CVE-2025-8715.

2ndQuadrant Postgres 13.21

Release date: 2025-05-09

This release is primarily an upstream merge.

Changes

Merged with community PostgreSQL 13.21. See the PostgreSQL 13.21 Release Notes for more information.

It also includes a security fix that was incorporated in 13.21: CVE-2025-4207.

2ndQuadrant Postgres 13.20

Release date: 2025-02-20

This release is primarily an upstream merge.

Changes

Merged with community PostgreSQL 13.20. See the PostgreSQL 13.20 Release Notes for more information.

2ndQuadrant Postgres 13.19

Release date: 2025-02-13

This release is primarily an upstream merge.

Migration

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Merged with community PostgreSQL 13.19. See the PostgreSQL 13.19 Release Notes for more information.

It also includes a security fix that was incorporated in 13.19: CVE-2025-1094.

2ndQuadrant Postgres 13.18

Release date: 2024-11-21

This release is primarily an upstream merge.

Merged with community PostgreSQL 13.18. See the PostgreSQL 13.18 Release Notes for more information.

It also includes the security fixes that were incorporated in 13.17:

And a remediation to issues caused by the 13.17 fix to CVE-2024-10978.

2ndQuadrant Postgres 13.16.1r1.1.19

Release date: 2024-08-22

This release is primarily a bug fix release. It contains a variety of improvements over the previous release.

Migration

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

A previous release introduced a new in_create field to the LogicalDecodingContext structure and changed its memory layout. This means that any code that expects the old layout will no longer be compatible. The release fixed the issue to ensure that the layout of previous database server versions is still compatible with the creation of a logical replication slot.

2ndQuadrant Postgres 13.16r1.1.18

Release date: 2024-08-08

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Added cleanup for incomplete transactions in reorder buffer after a crash (RT99636).
Merged the REL_13_16 tag of the community PostgreSQL code base.
Includes a fix for CVE-2024-7348 (Prevent unauthorized code execution during pg_dump) - see the PostgreSQL 13.16 Release Notes for more information.

2ndQuadrant Postgres 13.15r1.1.17

Release date: 2024-05-09

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Merged the REL_13_15 tag of the community PostgreSQL code base.

2ndQuadrant Postgres 13.14r1.1.16

Release date: 2024-02-08

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Merged the REL_13_14 tag of the community PostgreSQL code base.

2ndQuadrant Postgres 13.13r1.1.15

Release date: 2023-11-10

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Merged the REL_13_13 tag of the community PostgreSQL code base.

2ndQuadrant Postgres 13.12r1.1.14

Release date: 2023-08-10

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Merged the REL_13_12 tag of the community PostgreSQL code base.

2ndQuadrant Postgres 13.11r1.1.13

Release date: 2023-05-16

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Merged the REL_13_11 tag of the community PostgreSQL code base.

2ndQuadrant Postgres 13.9r1.1.12

Release date: 2023-02-14

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Merged the REL_13_10 tag of the community PostgreSQL code base.

2ndQuadrant Postgres 13.9r1.1.11

Release date: 2022-11-10

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Merged the REL_13_9 tag of the community PostgreSQL code base.

2ndQuadrant Postgres 13.8r1.1.10

Release date: 2022-08-11

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Merged the REL_13_8 tag of the community PostgreSQL code base.

2ndQuadrant Postgres 13.7r1.1.9

Release date: 2022-05-12

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Merged the REL_13_7 tag of the community PostgreSQL code base.

2ndQuadrant Postgres 13.6r1.1.8

Release date: 2022-02-10

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Merged the REL_13_6 tag of the community PostgreSQL code base.

2ndQuadrant Postgres 13.5r1.1.7

Release date: 2021-11-11

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Merged the REL_13_5 tag of the community PostgreSQL code base.

2ndQuadrant Postgres 13.4r1.1.6

Release date: 2021-08-17

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Merged the REL_13_4 tag of the community PostgreSQL code base.

2ndQuadrant Postgres 13.3r1.1.5

Release date: 2021-07-20

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Excluded LCR directory from base backup.

2ndQuadrant Postgres 13.3r1.1.4

Release date: 2021-05-18

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Merged the REL_13_3 tag of the community PostgreSQL code base. Includes security fixes.

2ndQuadrant Postgres 13.2r1.1.3

Release date: 2021-04-08

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Moved most of CAMO/Eager code out of 2QPG, adapted to upstream.
Improved synchronization between WAL decoder and sender for single decoder worker.
Fixed crash in selective base backup.
Fixed psql and pg_dump to be compatible with community PostgreSQL.
Lowered minimum fill factor for heap tables to 1.

2ndQuadrant Postgres 13.2r1.1.2

Release date: 2021-02-23

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Also, all extensions need to be recompiled.

Changes

Rebased to the REL_13_2 tag of the community PostgreSQL code base. Includes security fixes.
Changed FUNC_MAX_ARGS to 250.
libpq: Removed PQsslpassword().

2ndQuadrant Postgres 13.1r1.1.2

Release date: 2021-01-19

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Rebased to the REL_13_1 tag of the community PostgreSQL code base. Includes security fixes (CVE-2020-25694, CVE-2020-25695, CVE-2020-25696).
Various commits/fixes to bring parity with 2QPG11 feature sets. This is a beta release and contains various changes to bring about the same functionality as 2QPG11 vis-a-vis BDR and non-BDR features.

2ndQuadrant Postgres 13.0r1.1.1

Release date: 2020-11-05

This is the first release in the r1.1.x series of releases. This release contains a variety of improvements over PostgreSQL 13.0. For more information about new features in the core 13.0 release, see the Postgres 13 release notes.

Migration

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Rebased to the REL_13_0 tag of the community PostgreSQL code base.
Show a backtrace for PANIC messages by default even if guc is disabled.
Getting to know the stack trace for PANIC messages is handy for forensics. So show the backtrace for such messages regardless of whether the pg2q.backtrace_on_internal_error configuration parameter is enabled.
Provided a way to skip checking of NOT VALID constraints.
While NOT VALID constraints are normally checked and enforced for new rows being inserted/updated into the database, we provide an optional facility to skip the checks. This is useful for apply workers that may choose to skip the check, either because the check is done on the origin or because the check is known to potentially produce an ERROR and you instead want to rely on subsequent VALIDATE CONSTRAINT to catch violations.
Added a table-level option to control compression.
We now support a new table level-option, compress_tuple_target, which can be set to decide when to trigger compression on a tuple. Prior to this, the toast_tuple_target (or the compile time default) was used to decide whether to compress a tuple. But this was detrimental when a tuple is large enough and has a good compression ratio but not large enough to cross the toast threshold. We didn't compress such tuples, thus wasting a potentially good opportunity.
COPY FREEZE: Check if all tuples in a given page of a given table are frozen and visible, without doing any extensive checks.
We typically do this when we're doing table insertions in TABLE_INSERT_FROZEN mode (for example, COPY FREEZE). Since the relation isn't visible to any other transactions when running in this mode, we usually expect the pages to contain only tuples with frozen-xmin and invalid-xmax. But to guard against the case when our own transaction may have inserted regular tuples, which aren't marked frozen, in the table and for abundance of caution, we also do this check.
Added 2ndQPostgres configuration parameters to limit max tuple size and max field size.
The new pg2q.max_tuple_size parameter restricts the maximum before-TOASTing size that can be written to a table. This value is the total row width including the uncompressed width of all TOASTable VARLENA attributes.

Moved most of CAMO/Eager code out of 2QPG, adapted to upstream.
Improved synchronization between WAL decoder and sender for Single Decoder Worker.
Fixed crash in selective base backup.
Fixed psql and pg_dump to be compatible with community PostgreSQL.
Lowered minimum fill factor for heap tables to 1.

2ndQuadrant Postgres 13.2r1.1.2

Release date: 2021-02-23

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Also, all extensions need to be recompiled.

Changes

Rebased to the REL_13_2 tag of the community PostgreSQL code base. Includes security fixes.
Changed FUNC_MAX_ARGS to 250.
libpq: Removed PQsslpassword().

2ndQuadrant Postgres 13.1r1.1.2

Release date: 2021-01-19

This release contains a variety of improvements over the previous release.

Migration

This is a minor release and can be upgraded in place from previous 2ndQuadrant Postgres 13 releases. No additional migration tasks are needed.

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Rebased to the REL_13_1 tag of the community PostgreSQL code base. Includes security fixes (CVE-2020-25694, CVE-2020-25695, CVE-2020-25696).
Various commits/fixes to bring parity with 2QPG11 feature sets. This is a beta release and contains various changes to bring about the same functionality as 2QPG11 vis-a-vis BDR and non-BDR features.

2ndQuadrant Postgres 13.0r1.1.1

Release date: 2020-11-05

Migration

A dump/restore using pg_dumpall is required if you want to migrate data from any previous community PostgreSQL release.

Changes

Rebased to the REL_13_0 tag of the community PostgreSQL code base.
Show a backtrace for PANIC messages by default even if guc is disabled.
Getting to know the stack trace for PANIC messages is handy for forensics. So we now show the backtrace for such messages regardless of whether the pg2q.backtrace_on_internal_error configuration parameter is enabled.
Provided a way to skip checking of NOT VALID constraints.
While NOT VALID constraints are normally checked and enforced for new rows being inserted/updated into the database, we provide an optional facility to skip the checks. This is useful for apply workers that may choose to skip the check, either because the check is done on the origin or because the check is known to potentially produce an ERROR and you instead want to rely on a subsequent VALIDATE CONSTRAINT to catch violations.
Added a table-level option to control compression.
We now support a new table-level option, compress_tuple_target, which can be set to decide when to trigger compression on a tuple. Prior to this, toast_tuple_target (or the compile time default) was used to decide whether to compress a tuple. But this was detrimental when a tuple is large enough and has a good compression ratio but not large enough to cross the toast threshold. We didn't compress such tuples, thus wasting a potentially good opportunity.
COPY FREEZE: Check if all tuples in a given page of a given table are frozen and visible, without doing any extensive checks.
We typically do this when we're doing table insertions in TABLE_INSERT_FROZEN mode (for example, COPY FREEZE). Since the relation isn't visible to any other transactions when running in this mode, we usually expect the pages to contain only tuples with frozen-xmin and invalid-xmax. But to guard against the case when our own transaction may have inserted regular tuples, which aren't marked frozen, in the table and for abundance of caution, we do this check also.
Added 2ndQPostgres configuration parameters to limit max tuple size and max field size.
The new pg2q.max_tuple_size parameter restricts the maximum before-TOASTing size that can be written to a table. This is the total row width including the uncompressed width of all TOASTable VARLENA attributes.

← Prev

2ndQuadrant Postgres/EDB Postgres Extended Server 13

↑ Up

2ndQuadrant Postgres/EDB Postgres Extended Server 13