Re: Report error position in partition bound check

From: Alexandra Wang <lewang(at)pivotal(dot)io>
To: Ashutosh Bapat <ashutosh(dot)bapat(at)2ndquadrant(dot)com>
Cc: Amit Langote <amitlangote09(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Ashwin Agrawal <aagrawal(at)pivotal(dot)io>
Subject: Re: Report error position in partition bound check
Date: 2020-04-10 21:50:17
Message-ID: CACiyaSpQ8BrNn+e_8i59iNRJxZ0CufOVe2kYm1qcujg68WqdQg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 10, 2020 at 8:37 AM Ashutosh Bapat <
ashutosh(dot)bapat(at)2ndquadrant(dot)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.

Attachment Content-Type Size
v2-0002-Improve-check-new-partition-bound-error-position-.patch text/x-patch 15.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jesse Zhang 2020-04-10 22:01:43 Re: Properly mark NULL returns in numeric aggregates
Previous Message Andres Freund 2020-04-10 21:48:05 Re: pg_validatebackup -> pg_verifybackup?