Re: Performance issues

From: Varadharajan Mukundan <srinathsmn(at)gmail(dot)com>
To: vjoshi(at)zetainteractive(dot)com
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Performance issues
Date: 2015-03-13 13:10:00
Message-ID: CACKkDGETLNUON-bLM0gCo_r-+ts3Q29aQwmargv1Usi=PgQvVg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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)

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Mel Llaguno 2015-03-13 19:18:30 Anyone have experience using PG on a NetApp All-Flash FAS8000?
Previous Message Vivekanand Joshi 2015-03-13 13:03:22 Re: Performance issues