On 1/12/21 8:51 AM, Голубева Яна wrote:
> Values for the key partitioning column are generated randomly and I
> can't predict their distribution between ranges.
> If I just create some ranges I won't have any guarantee that
> partitions will have similar amount of data. It is possible that I
> will have 2 or 3 extremely big partitions and a bit of data in others.
> Thank you,
> Iana Golubeva
>
>
> 12.01.2021, 17:55, "Michael Lewis" <mlewis(at)entrata(dot)com>:
>
> On Tue, Jan 12, 2021 at 1:21 AM Голубева Яна <ishsha(at)yandex(dot)ru
> <mailto:ishsha(at)yandex(dot)ru>> wrote:
>
> List or range partitioning isn't suitable for my case.
> I am using a column of numeric(20) type as a base for
> partitioning. The values of the column are generated randomly.
> So there will be too many partitions if I use list
> partitioning as is.
>
>
> Sorry, but why is range not suited for this? It would seem fairly
> trivial to create 50 or 1000 partitions to break up the range of
> values allowed by your field definition.
>
Doesn't sound like a good definition of random.