From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, 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-16 01:35:43 |
Message-ID: | CA+TgmoZYJM=SWHE6ANpZCKTR-X6njSPSKwHW97bUX8yLjFH1Kg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Thu, Sep 14, 2017 at 12:59 PM, David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> I think we are being consistent as a project by enforcing strictness of
> input in this situation so I'll toss my +0.5/+1 here as well.
All right, since all three new votes are going the same direction with
this, committed the patch for that.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-09-16 01:38:01 | pgsql: After a MINVALUE/MAXVALUE bound, allow only more of the same. |
Previous Message | Robert Haas | 2017-09-16 01:34:21 | pgsql: After a MINVALUE/MAXVALUE bound, allow only more of the same. |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2017-09-16 01:37:12 | Re: Clarification in pg10's pgupgrade.html step 10 (upgrading standby servers) |
Previous Message | Alexander Korotkov | 2017-09-15 23:51:35 | Re: Should we cacheline align PGXACT? |