yes, it doesn't look good. and it seems that statistics aren't accurate:
GroupAggregate (cost=271794.39..330553.67 rows=215630 width=152) (actual
time=30.641..37.303 rows=2792 loops=1)
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
: pgsql-gene...@postgresql.org
Subject: Re: How Many Partitions are Good Performing
I've run once a test on my laptop because was curious as well. From my results
(on laptop - 16GB RAM, 4 cores) the upper limit was 12k. Above it planning time
was unbearable high - much higher than execution
I've run once a test on my laptop because was curious as well. From my
results (on laptop - 16GB RAM, 4 cores) the upper limit was 12k. Above it
planning time was unbearable high - much higher than execution time. It's
been tested on 9.5
--
Sent from: http://www.postgresql-archive.org/PostgreSQL
2018-01-09 18:15 GMT+01:00 Andrew Staller :
> This is the blog post that Rakesh referenced:
> https://blog.timescale.com/time-series-data-postgresql-
> 10-vs-timescaledb-816ee808bac5
>
> Please note, this analysis is done in the context of working with
> time-series data, where 1000s of chunks is
value a partition.
Regards,
Virendra
From: Andrew Staller [mailto:and...@timescale.com]
Sent: Tuesday, January 09, 2018 12:15 PM
To: Rakesh Kumar
Cc: Kumar, Virendra; pgsql-gene...@postgresql.org
Subject: Re: How Many Partitions are Good Performing
This is the blog post that Rakesh referenced:
https
This is the blog post that Rakesh referenced:
https://blog.timescale.com/time-series-data-postgresql-10-vs-timescaledb-816ee808bac5
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 w
On Tue, Jan 09, 2018 at 12:54:18AM +0100, Rakesh Kumar wrote:
> 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
You should have read carefully what I wrote. 1000 is not an upper limit.
1000 partition is the number after which performance starts dropping .
There is a blog in www.timescale.com which also highlights the same.
Sent: Monday, January 08, 2018 at 6:20 PM
From: "Kumar, Virendra"
To: "pgsql