| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partition b |
| Date: | 2017-09-13 13:51:19 |
| Message-ID: | CA+TgmoaKvyYywmRbWBPRVy+pfjcDF--_U01e0pujq9QyWKXjaA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, Sep 13, 2017 at 5:05 AM, Amit Langote
<Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>> So thinking about this afresh, my preference would actually be to just
>> canonicalise the values stored rather than erroring out.
>
> Coincidentally, I just wrote the patch for canonicalizing stored values,
> instead of erroring out. Please see attached if that's what you were
> thinking too.
Coincidentally, I wrote a patch for this too, but mine goes back to
rejecting MINVALUE or MAXVALUE followed by anything else.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| Attachment | Content-Type | Size |
|---|---|---|
| enforce-minmaxvalue-consistency.patch | application/octet-stream | 21.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-09-13 13:53:10 | Re: Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partition b |
| Previous Message | Bruce Momjian | 2017-09-13 13:22:31 | pgsql: docs: adjust "link mode" mention in pg_upgrade streaming steps |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-09-13 13:53:10 | Re: Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partition b |
| Previous Message | Bruce Momjian | 2017-09-13 13:26:27 | Re: Clarification in pg10's pgupgrade.html step 10 (upgrading standby servers) |