| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | 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>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: dubious error message from partition.c |
| Date: | 2017-08-09 20:59:21 |
| Message-ID: | 26817.1502312361@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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".
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Remi Colinet | 2017-08-09 21:03:58 | Re: [PATCH v3] pg_progress() SQL function to monitor progression of long running SQL queries/utilities |
| Previous Message | Alvaro Herrera | 2017-08-09 20:38:21 | Re: dubious error message from partition.c |