On Thu, Aug 23, 2012 at 6:46 AM, Merlin Moncure <mmoncure@xxxxxxxxx> wrote: > On Wed, Aug 22, 2012 at 6:06 PM, Nick <nboutelier@xxxxxxxxx> wrote: >> I have a table with 40 million rows and haven't had any performance issues yet. >> >> Are there any rules of thumb as to when a table starts getting too big? >> >> For example, maybe if the index size is 6x the amount of ram, if the table is 10% of total disk space, etc? > > Well, that begs the question: ...and do what? I guess you probably > mean partitioning. > > Partitioning doesn't reduce index size -- it makes total index size > *bigger* since you have to duplicate higher nodes in the index -- > unless you can exploit the table structure around the partition so > that less fields have to be indexed. Depending on the operation it may make the effective index size bigger or smaller. For example if querying only one child table your effective index size is much smaller. However, if you are worried about that, partial indexes rock :-D Best Wishes, Chris Travers -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
