| 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 16:59:49 |
| Message-ID: | CACiyaSo90gUhmWPfwwxSA8=ps6HZh6TjKOOdNgE8ihMbmE=hww@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 10 Apr 2020 at 14:31, Amit Langote <amitlangote09(at)gmail(dot)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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2020-04-10 17:30:47 | Re: proposal: schema variables |
| Previous Message | Robert Haas | 2020-04-10 16:20:01 | Re: where should I stick that backup? |