Re: Report error position in partition bound check - Mailing list pgsql-hackers

From Alexandra Wang
Subject Re: Report error position in partition bound check
Date
Msg-id DM6PR05MB692465B221C78E971542F745B0600@DM6PR05MB6924.namprd05.prod.outlook.com
Whole thread Raw
In response to Re: Report error position in partition bound check  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
> On 2 July 2020, at 06:39, Daniel Gustafsson <daniel@yesql.se> wrote:
> > On 10 Apr 2020, at 23:50, Alexandra Wang <lewang@pivotal.io> wrote:
>
> > On Fri, Apr 10, 2020 at 8:37 AM Ashutosh Bapat <ashutosh.bapat@2ndquadrant.com <mailto: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.
>
> This patch fails to apply to HEAD due to conflicts in the create_table expected
> output.  Can you please submit a rebased version?  I'm marking the CF entry
> Waiting on Author in the meantime.

Thank you Daniel. Here's the rebased patch. I also squashed the two
patches into one so it's easier to review.

--
Alex

Attachment

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: min_safe_lsn column in pg_replication_slots view
Next
From: Justin Pryzby
Date:
Subject: Re: proposal: possibility to read dumped table's name from file