| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Alexandra Wang <lewang(at)pivotal(dot)io> |
| Cc: | Ashutosh Bapat <ashutosh(dot)bapat(at)2ndquadrant(dot)com>, 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-07-02 13:39:09 |
| Message-ID: | FE6EE039-E943-4B9A-84F1-512F193A5464@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 10 Apr 2020, at 23:50, Alexandra Wang <lewang(at)pivotal(dot)io> wrote:
> On Fri, Apr 10, 2020 at 8:37 AM Ashutosh Bapat <ashutosh(dot)bapat(at)2ndquadrant(dot)com <mailto: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.
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.
cheers ./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2020-07-02 13:46:11 | Re: Remove Deprecated Exclusive Backup Mode |
| Previous Message | Daniel Gustafsson | 2020-07-02 13:29:25 | Re: Reducing WaitEventSet syscall churn |