On Tue, Jan 12, 2021 at 1:21 AM Голубева Яна <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.