Re:Re: Re: Fix incorrect column name in error message for range partition bound check
myzhen <zhenmingyang@yeah.net>
From: myzhen <zhenmingyang@yeah.net>
To: "Eden Wang" <wanglintao_cn@163.com>
Cc: "zhibin wang" <killerwzb@gmail.com>, pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-01-08T12:03:41Z
Lists: pgsql-hackers
Um, yes, as long as this problem can be solved, that's fine.
patch v2 may do less and reduce unnecessary transforms,
but the impact on DDL is minimal and may not need to be considered.
At 2026-01-08 08:36:06, "Eden Wang" <wanglintao_cn@163.com> wrote:
Hi myzhen,
Hmmm...personally, I prefer the first patch – it resolves this issue and is more concise.
Eden Wang
Commits
-
Fix possible incorrect column reference in ERROR message
- a65995947cfe 14.21 landed
- 3ad05640b67f 15.16 landed
- 821c4d27bca2 16.12 landed
- 84b787ae66e6 17.8 landed
- c35e5dd9ae97 18.2 landed
- 349107537d22 19 (unreleased) landed