> > IMO, If there is a good reason to allow the other pgbench > > tables to be partitioned, that may be better to think > > about. I am not sure there is though. > > see this thread [1] proposing partitioning pgbench_history last year. > > [1] https://www.postgresql.org/message-id/flat/CAAKRu_Zo8ST-Qk8VQ4KFkbMQcqJsQQz5r%2BYRRbecS3avgkoZhw%40mail.gmail.com#ca9397c201ed483cb02f07dcaaa2773c I don't see the partitioning history being beneficial for the built-in workloads, but it may make sense to partition the history table if you intend to run a custom benchmark that includes reading specific accounts from the history table. Partitioning by date range as you suggest [1] makes sense as well. Maybe It will be good to provide more flexibility around which tables to partition and the partition key(s) for the pgbench schema so to benchmark different partition strategies. [1] https://www.postgresql.org/message-id/CAAKRu_Zo8ST-Qk8VQ4KFkbMQcqJsQQz5r%2BYRRbecS3avgkoZhw%40mail.gmail.com Regards, Sami
pgsql-hackers by date:
Соглашаюсь с условиями обработки персональных данных