Re: [HACKERS] Multi column range partition table - Mailing list pgsql-hackers

From Dean Rasheed
Subject Re: [HACKERS] Multi column range partition table
Date
Msg-id CAEZATCUHu+pFF8yuJSVqyy24aeeXb+6d=h6nrf=nw+25Hq=zbg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Multi column range partition table  (Joe Conway <mail@joeconway.com>)
Responses Re: [HACKERS] Multi column range partition table
Re: [HACKERS] Multi column range partition table
Re: [HACKERS] Multi column range partition table
List pgsql-hackers
On 6 July 2017 at 22:43, Joe Conway <mail@joeconway.com> wrote:
> I agree we should get this right the first time and I also agree with
> Dean's proposal, so I guess I'm a +2
>

On 7 July 2017 at 03:21, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> wrote:
> +1 to releasing this syntax in PG 10.
>

So, that's 3 votes in favour of replacing UNBOUNDED with
MINVALUE/MAXVALUE for range partition bounds in PG 10. Not a huge
consensus, but no objections either. Any one else have an opinion?

Robert, have you been following this thread?

I was thinking of pushing this later today, in time for beta2.

Regards,
Dean



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: [HACKERS] GSoC 2017: Foreign Key Arrays
Next
From: Noah Misch
Date:
Subject: Re: [HACKERS] pg_stop_backup(wait_for_archive := true) on standby server