Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE insteadof UNBOUNDED for range partition b - Mailing list pgsql-hackers

From Dean Rasheed
Subject Re: [HACKERS] Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE insteadof UNBOUNDED for range partition b
Date
Msg-id CAEZATCUuodg7j+EkLUaTfrKtqjE4mz8s8r9Y1gO9o4ibH_6FdQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE insteadof UNBOUNDED for range partition b  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Tree view 
On 13 September 2017 at 14:51, Robert Haas <robertmhaas@gmail.com> wrote:
> Coincidentally, I wrote a patch for this too, but mine goes back to
> rejecting MINVALUE or MAXVALUE followed by anything else.
>

LGTM, if we decide to go this way.

One minor review comment -- you missed an example code snippet using
(MINVALUE, 0) further down the page in create_table.sgml, which needs
updating.

Regards,
Dean


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Dean Rasheed
Date:
Subject: Re: [HACKERS] Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE insteadof UNBOUNDED for range partition b
Next
From: Dean Rasheed
Date:
Subject: [HACKERS] Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE instead ofUNBOUNDED for range partition b