We will not be doing time scaling but we have list of value based of which we will be partitioning the table and list is something around 7500 now.
For short term we are thinking of putting around a thousand partitions and when PG11 releases we will go for each value a partition.
Regards,
Virendra
From: Andrew Staller [mailto:andrew@timescale.com] Sent: Tuesday, January 09, 2018 12:15 PM To: Rakesh Kumar Cc: Kumar, Virendra; pgsql-general@postgresql.org Subject: Re: How Many Partitions are Good Performing
Please note, this analysis is done in the context of working with time-series data, where 1000s of chunks is not uncommon because of the append-mostly nature of the workload.
Can somebody tell us how many partitions are good number without impacting the performance. We are hearing around a thousand, is that a limit. Do we have plan to increase the number of partitions for a table. We would appreciate if somebody can help us with this? Regards, Virendra ------------------------------------------------------------
This message is intended only for the use of the addressee and may contain information that is PRIVILEGED AND CONFIDENTIAL.
If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify the sender immediately. Thank you.
This message is intended only for the use of the addressee and may contain information that is PRIVILEGED AND CONFIDENTIAL.
If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify the sender immediately. Thank you.