Re: Extend pgbench partitioning to pgbench_history

Please discard the previous patch and use this one (it had a leftover
comment from an initial attempt to limit this to hash case).

Thanks,
Gabriele

On Thu, 30 Nov 2023 at 11:29, Gabriele Bartolini <
gabriele(dot)bartolini(at)enterprisedb(dot)com> wrote:

> Hi there,
>
> While benchmarking a new feature involving tablespace support in
> CloudNativePG (Kubernetes operator), I wanted to try out the partitioning
> feature of pgbench. I saw it supporting both range and hash partitioning,
> but limited to pgbench_accounts.
>
> With the attached patch, I extend the partitioning capability to the
> pgbench_history table too.
>
> I have been thinking of adding an option to control this, but I preferred
> to ask in this list whether it really makes sense or not (I struggle indeed
> to see use cases where accounts is partitioned and history is not).
>
> Please let me know what you think.
>
> Thanks,
> Gabriele
> --
> Gabriele Bartolini
> Vice President, Cloud Native at EDB
> enterprisedb.com
>

--
Gabriele Bartolini
Vice President, Cloud Native at EDB
enterprisedb.com