| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: dubious error message from partition.c |
| Date: | 2017-08-10 02:14:00 |
| Message-ID: | cd92fa65-75f4-22c8-14c8-e8467948c8c2@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017/08/10 5:59, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
>> Dean Rasheed wrote:
>>> There was an earlier suggestion to use "greater than or equal to". I
>>> think that would work quite well:
>
>> Is it possible to detect the equality case specifically and use a
>> different errdetail? Something like "the lower bound %s is equal to the
>> upper bound" (obviously without including both in the message.)
>
> That seems like overkill. I'm good with "greater than or equal to".
Attached updated patch has "greater than or equal to".
Thanks,
Amit
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Fix-error-message-when-apprently-empty-range-bound-i.patch | text/plain | 6.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2017-08-10 03:43:07 | Re: Small code improvement for btree |
| Previous Message | Amit Langote | 2017-08-10 02:11:56 | Re: expanding inheritance in partition bound order |