pgsql: Work around broken TimescaleDB code

From: Noah Misch <noah(at)leadboat(dot)com>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Work around broken TimescaleDB code
Date: 2026-11-09 14:21:56
Message-ID: E1xQQFw-000000003ZF-38sw@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Work around broken TimescaleDB code

TimescaleDB crashes if an attribute option is present during chunk
creation as part of a DDL command, due to calling AlterTableInternal()
without having set up event trigger state. With the introduction of
attribute versioning, which stores the version in an internal attribute
option in the back-branches, attribute options are much more common.

The breakage is easy enough to work around, so do that.

This will only be applied to release branches, as this is clearly a bug
in TimescaleDB.

Security: CVE-2026-6460
Backpatch-through: 14-19

Branch
------
REL_19_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/9c5f9a41dc62eab62f46ada5f1c23ee4eb554552
Author: Andres Freund <andres(at)anarazel(dot)de>

Modified Files
--------------
src/backend/commands/event_trigger.c | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Noah Misch 2026-11-09 14:21:57 pgsql: Fix reusing large allocations in generation memory contexts
Previous Message Noah Misch 2026-11-09 14:21:55 pgsql: Fix type confusion with materialized set-returning functions