summaryrefslogtreecommitdiff
path: root/src/test/regress/expected/numeric_big.out
diff options
context:
space:
mode:
authorDavid Rowley <drowley@postgresql.org>2026-01-09 11:01:36 +1300
committerDavid Rowley <drowley@postgresql.org>2026-01-09 11:01:36 +1300
commit349107537d22a04c94c6fec5b993461178b39c13 (patch)
tree23094c2ece14a316110bab410a191681c2cbbcb2 /src/test/regress/expected/numeric_big.out
parentb8ccd29152f5e00250869499daab226f6ce55fdd (diff)
Fix possible incorrect column reference in ERROR messageHEADorigin/masterorigin/HEADmaster
When creating a partition for a RANGE partitioned table, the reporting of errors relating to converting the specified range values into constant values for the partition key's type could display the name of a previous partition key column when an earlier range was specified as MINVALUE or MAXVALUE. This was caused by the code not correctly incrementing the index that tracks which partition key the foreach loop was working on after processing MINVALUE/MAXVALUE ranges. Fix by using foreach_current_index() to ensure the index variable is always set to the List element being worked on. Author: myzhen <zhenmingyang@yeah.net> Reviewed-by: zhibin wang <killerwzb@gmail.com> Discussion: https://postgr.es/m/273cab52.978.19b96fc75e7.Coremail.zhenmingyang@yeah.net Backpatch-through: 14
Diffstat (limited to 'src/test/regress/expected/numeric_big.out')
0 files changed, 0 insertions, 0 deletions