Horton

Re: Report error position in partition bound check

Alexandra Wang <lewang@pivotal.io>

View thread View on postgr.es
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-10T16:59:49Z
Lists: pgsql-hackers 
On Fri, 10 Apr 2020 at 14:31, Amit Langote <amitlangote09@gmail.com> wrote:
> I agree with that.  Tried that in the attached 0002, although trying
> to get the cursor to point to exactly the offending column seems a bit
> tough for partition overlap errors.  The patch does allow to single
> out which one of the lower and upper bounds is causing the overlap
> with an existing partition, which is better than now and seems helpful
> enough.
>
> Also, updated Alexandra's patch to incorporate Ashutosh's comment such
> that we get the same output with ATTACH PARTITION commands too.

Thank you Amit for updating the patches, the cursor looks much helpful now.
I
created the commitfest entry https://commitfest.postgresql.org/28/2533/

Commits

  1. Improve error cursor positions for problems with partition bounds.