Re: Empty Range Bound Specified for Partition

From: ramsiddu007 <ramsiddu007(at)gmail(dot)com>
To: haramrae(at)gmail(dot)com
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Empty Range Bound Specified for Partition
Date: 2018-11-22 09:10:19
Message-ID: CA+zEy7_w1RQdRSwsMxV_aWAjEuM-WKjbUH3qGzL3YrV5bX8JGg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thank you for the clarification.

On Thu, 22 Nov 2018 at 13:30, Alban Hertroys <haramrae(at)gmail(dot)com> wrote:

>
> > On 22 Nov 2018, at 7:21, ramsiddu007 <ramsiddu007(at)gmail(dot)com> wrote:
> >
> > pgsql> create table test_upto_100 partition of test_parent_partition
> > for values from ('51') to ('100');
> >
> > It was showing error like this..
> >
> > ERROR: empty range bound specified for partition "test_upto_100"
> > DETAIL: Specified lower bound ('51') is greater than or equal to upper
> bound ('100').
> > SQL state: 42P17
> >
> >
> > I am not getting, please give me cause of this and
> solution.
>
> Alphabetically, '1' comes before '5', so '100' comes before '51'.
> Numerically, you would get what you intended, but you're not partitioning
> on numbers but on strings instead and those sort alphabetically: '1', '10',
> '100', '11', '2', '3', '51', etc.
>
> Alban Hertroys
> --
> If you can't see the forest for the trees,
> cut the trees and you'll find there is no forest.
>
>

--
*Best Regards:*
Ramanna Gunde

*Don't complain about the HEAT,*

*PLANT A .*

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Madan Kumar 2018-11-22 11:24:06 Invoking user of the function with SECURITY DEFINER
Previous Message Alban Hertroys 2018-11-22 08:00:28 Re: Empty Range Bound Specified for Partition