Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDEDfor range partition b - Mailing list pgsql-committers

From Dean Rasheed
Subject Re: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDEDfor range partition b
Date
Msg-id CAEZATCUiRKQY=qW+mBy=R3xuHkqBNTxM6dprCMjVhiTufSCk+A@mail.gmail.com
Whole thread Raw
In response to [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partitionb  (Dean Rasheed <dean.a.rasheed@gmail.com>)
List pgsql-committers
On 21 July 2017 at 09:24, Dean Rasheed <dean.a.rasheed@gmail.com> wrote:
> Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partition bounds.
>

Hmm, looks like the buildfarm doesn't like this.

It looks like the order of partitions listed by \d+ isn't entirely
predictable ... looking into it now.

Regards,
Dean


pgsql-committers by date:

Previous
From: Dean Rasheed
Date:
Subject: [COMMITTERS] pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partitionb
Next
From: Dean Rasheed
Date:
Subject: [COMMITTERS] pgsql: Make the new partition regression tests locale-independent.