| From: | "Martin French" <Martin(dot)French(at)romaxtech(dot)com> |
|---|---|
| To: | Bill Moran <wmoran(at)potentialtech(dot)com> |
| Cc: | Nick <nboutelier(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, pgsql-general-owner(at)postgresql(dot)org |
| Subject: | Re: At what point does a big table start becoming too big? |
| Date: | 2012-08-23 13:51:19 |
| Message-ID: | OFA24FEEF4.731FDC31-ON80257A63.004C03F4-80257A63.004C1C7F@LocalDomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
<html><body><p><tt><font size="2"><br>> > ><br>> > > I have a table with 40 million rows and haven't had any performance<br>> > > issues yet.<br>> > ><br>> > > Are there any rules of thumb as to when a table starts getting too big?<br>> > ><br>> > > For example, maybe if the index size is 6x the amount of ram, if the<br>> > > table is 10% of total disk space, etc?<br>> > <br>> > My rule here is that a table is too big when performance starts <br>> degrading beyond an acceptable level.<br>> <br>> The challenge there is that if you wait until performance degrades<br>> beyond an acceptable level, you've allowed yourself to get into a<br>> situation where clients are upset and frustrated, and fixing the<br>> problem is difficult because there's so much data to manipulate to<br>> rearrange things.<br>> <br>Apologies, I could/should have phrased that better..</font></tt><br><br><tt><font size="2">My rule here is that a table is too big when performance starts degrading beyond a MEASURABLE level. :)</font></tt><br><br><tt><font size="2">Cheers</font></tt><br><br><tt><font size="2">Martin </font></tt><br><font face="sans-serif">=============================================
Romax Technology Limited
Rutherford House
Nottingham Science & Technology Park
Nottingham,
NG7 2PZ
England
Telephone numbers:
+44 (0)115 951 88 00 (main)
For other office locations see:
http://www.romaxtech.com/Contact
=================================
===============
E-mail: info(at)romaxtech(dot)com
Website: www.romaxtech.com
=================================
================
Confidentiality Statement
This transmission is for the addressee only and contains information that is confidential and privileged.
Unless you are the named addressee, or authorised to receive it on behalf of the addressee
you may not copy or use it, or disclose it to anyone else.
If you have received this transmission in error please delete from your system and contact the sender. Thank you for your cooperation.
=================================================</font>
</body></html>
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/html | 2.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2012-08-23 13:52:03 | Re: Can column name aliases be supported? |
| Previous Message | Tom Lane | 2012-08-23 13:51:07 | Re: Rules, Windows and ORDER BY |