From: | Gabriele Bartolini <gabriele(dot)bartolini(at)enterprisedb(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Extend pgbench partitioning to pgbench_history |
Date: | 2023-11-30 10:29:15 |
Message-ID: | CA+VUV5q9=N64fduq660bvFGQeFQcfqU2xh+XR_1OaPj87io3sg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
Attachment | Content-Type | Size |
---|---|---|
0001-Include-pgbench_history-in-partitioning-method-for-p.patch | application/octet-stream | 7.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Shubham Khanna | 2023-11-30 10:32:28 | Re: Various small doc improvements; plpgsql, schemas, permissions, oidvector |
Previous Message | Amit Kapila | 2023-11-30 10:11:19 | Re: Is this a problem in GenericXLogFinish()? |