Re: Performance issues - Mailing list pgsql-performance

From Vivekanand Joshi
Subject Re: Performance issues
Date
Msg-id CANwLwatODrcwDgO+JXG-L=jJJQTucvUrur01E-y_tE_PT8i7kQ@mail.gmail.com
Whole thread Raw
In response to Re: Performance issues  (Varadharajan Mukundan <srinathsmn@gmail.com>)
Responses Re: Performance issues
List pgsql-performance

I am really worried about the performance of PostgreSQL as we have almost 1.5 billion records in promotion history table. Do you guys really think PostgreSQL can handle this much load. We have fact tables which are more than 15 GB in size and we have to make joins with those tables in almost every query.

On 13 Mar 2015 18:40, "Varadharajan Mukundan" <srinathsmn@gmail.com> wrote:
If the s_f_promotion_history table will have a explosive growth, then its worth considering partitioning by date and using constraint exclusion to speed up the queries. Else, it makes sense to get started with multiple partial index (like, have a index for each week or something like that. You may want to start with a coarse grain timeline for the index and then fine grain it based on the needs)

pgsql-performance by date:

Previous
From: Mel Llaguno
Date:
Subject: Anyone have experience using PG on a NetApp All-Flash FAS8000?
Next
From: Tomas Vondra
Date:
Subject: Re: Performance issues