Horton

Re:Re: Fix incorrect column name in error message for range partition bound check

myzhen <zhenmingyang@yeah.net>

View thread View on postgr.es
From: myzhen <zhenmingyang@yeah.net>
To: "zhibin wang" <killerwzb@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2026-01-07T09:50:28Z
Lists: pgsql-hackers

Attachments

Hi zhibin,


By the way, based on the context, once a column is set to MINVALUE or MAXVALUE, the values of the remaining columns must be the same. However, I noticed that 'validateInfiniteBounds' is only invoked after all boundary value transformations are completed. Perhaps we can perform the validity check for infinite boundary values earlier. In this way, we can not only avoid this error but also achieve timely "short-circuit" — because any non-MINVALUE transformation performed after MINVALUE is essentially meaningless overhead. ideas?


Thanks, I think it makes some sense, so I tried to make the second version.

Commits

  1. Fix possible incorrect column reference in ERROR message