Re: At what point does a big table start becoming too big? - Mailing list pgsql-general

From Martin French
Subject Re: At what point does a big table start becoming too big?
Date
Msg-id OFA24FEEF4.731FDC31-ON80257A63.004C03F4-80257A63.004C1C7F@LocalDomain
Whole thread Raw
In response to Re: At what point does a big table start becoming too big?  (Bill Moran <wmoran@potentialtech.com>)
List pgsql-general
> > >> > > I =
have a table with 40 million rows and haven't had any performance> &=
gt; > issues yet.> > >> > > Are there any rule=
s 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?> &=
gt; > > My rule here is that a table is too big when performance =
starts > degrading beyond an acceptable level.> > The =
challenge there is that if you wait until performance degrades> beyo=
nd an acceptable level, you've allowed yourself to get into a> situa=
tion where clients are upset and frustrated, and fixing the> problem=
 is difficult because there's so much data to manipulate to> rearran=
ge things.> Apologies, I could/should have phrased that better..=
My rule here is that a table is to=
o big when performance starts degrading beyond a MEASURABLE level. :)</font=
>Cheers<font size=
=3D"2">Martin =3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Romax Technology Limited
Rutherford House
Nottingham Science & Technology Park
Nottingham,=20
NG7 2PZ
England

Telephone numbers:
+44 (0)115 951 88 00 (main)

For other office locations see:
http://www.romaxtech.com/Contact
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
E-mail: info@romaxtech.com
Website: www.romaxtech.com
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Confidentiality Statement
This transmission is for the addressee only and contains information that i=
s confidential and privileged.
Unless you are the named addressee, or authorised to receive it on behalf o=
f the addressee=20
you may not copy or use it, or disclose it to anyone else.=20
If you have received this transmission in error please delete from your sys=
tem and contact the sender. Thank you for your cooperation.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</f=
ont>

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Rules, Windows and ORDER BY
Next
From: Craig Ringer
Date:
Subject: Re: Can column name aliases be supported?