| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
| Cc: | 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:53:10 |
| Message-ID: | CA+TgmoYUSpHi3jRQxvdDK3kgNbZT44GHA2MEVB9ez=3p9aNHUQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, Sep 13, 2017 at 4:51 AM, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> wrote:
> A drawback to doing this is that we lose compatibility with syntaxes
> supported by other databases, which was part of the reason for
> choosing the terms MINVALUE and MAXVALUE in the first place.
>
> So thinking about this afresh, my preference would actually be to just
> canonicalise the values stored rather than erroring out.
Can you be more specific about what other databases do here? Which
other systems support MINVALUE/MAXVALUE, and what are their respective
behaviors in this situation?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-09-13 14:13:37 | pgsql: doc: Remove incorrect SCRAM protocol documentation |
| Previous Message | Robert Haas | 2017-09-13 13:51:19 | Re: Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partition b |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jesper Pedersen | 2017-09-13 13:54:53 | Re: POC: Cache data in GetSnapshotData() |
| Previous Message | Robert Haas | 2017-09-13 13:51:19 | Re: Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partition b |