Re: pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partition b

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partition b
Date: 2017-07-21 08:36:36
Message-ID: CAEZATCUiRKQY=qW+mBy=R3xuHkqBNTxM6dprCMjVhiTufSCk+A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 21 July 2017 at 09:24, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Dean Rasheed 2017-07-21 09:20:53 pgsql: Make the new partition regression tests locale-independent.
Previous Message Dean Rasheed 2017-07-21 08:24:37 pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partition b

Browse pgsql-hackers by date

  From Date Subject
Next Message Alik Khilazhev 2017-07-21 08:43:31 Re: [WIP] Zipfian distribution in pgbench
Previous Message Dean Rasheed 2017-07-21 08:24:37 pgsql: Use MINVALUE/MAXVALUE instead of UNBOUNDED for range partition b