On Sat, Jul 14, 2012 at 11:50 AM, B Sreejith <bsreejithin@xxxxxxxxx> wrote: > Dear All, > Thanks alot for all the invaluable comments. Additionally to Craig's excellent advice to measurements there's something else you can do: with the knowledge of the queries your application fires against the database you can evaluate your schema and index definitions. While there is no guarantee that your application will scale well if all indexes are present you believe need to be present based on that inspection, you can pretty easily identify tables with can be improved. These are tables which a) are known to grow large and b) do not have indexes nor no indexes which support the queries your application does against these tables which will result in full table scans. Any database which scales in size will sooner or later hit a point where full table scans of these large tables will be extremely slow. If these queries are done during regular operation (and not nightly maintenance windows for example) then you pretty surely have identified a show stopper. Kind regards robert -- remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/ -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
