Re: Report error position in partition bound check
Alexandra Wang <lewang@pivotal.io>
From: Alexandra Wang <lewang@pivotal.io>
To: Ashutosh Bapat <ashutosh.bapat@2ndquadrant.com>
Cc: Amit Langote <amitlangote09@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>,
PostgreSQL mailing lists <pgsql-hackers@postgresql.org>,
Ashwin Agrawal <aagrawal@pivotal.io>
Date: 2020-04-10T21:50:17Z
Lists: pgsql-hackers
Attachments
- v2-0002-Improve-check-new-partition-bound-error-position-.patch (text/x-patch) patch v2-0002
On Fri, Apr 10, 2020 at 8:37 AM Ashutosh Bapat < ashutosh.bapat@2ndquadrant.com> wrote: > for a multi-key value the ^ > points to the first column and the reader may think that that's the > problematci column. Should it instead point to ( ? I attached a v2 of Amit's 0002 patch to also report the exact column for the partition overlap errors.
Commits
-
Improve error cursor positions for problems with partition bounds.
- 6b2c4e59d016 14.0 landed