Re: improve performance in a big table

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



A.Burbello a écrit :
Hi people,

I have a case and I got a doubt what should be the
best ways.

One table has more than 150 million of rows, and I
thought that could divided by state.
For each row has person ID, state and other
informations, but the search would be done only by
person ID (number column).

I can improve the query by putting index in that
column, but is there any other ways?

Thank you.




      Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento!
http://br.mail.yahoo.com/

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
       message can get through to the mailing list cleanly

Hello

I also studies how to improve performances on big tables.
Like you , I don't know how to improve without index. It's the only way I found . I find postgresql is fast on small table but I got real performance problem when increases the number of rows Do anyone know if there is specific postgresql tuning parameters in .conf file for big tables ?

max_fsm_pages ?
max_fsm_relations ?


Olivier



--
Olivier BOISSARD
olivier.boissard@xxxxxxxxx

CERENE SERVICES SA
3, rue Archimède
10600 La Chapelle-Saint-Luc - France
Tel : 33 (0)3 25 74 11 78
Fax : 33 (0)3 25 78 39 67
----------------------------
"Ce message peut contenir des informations confidentielles et/ou
protégées. Il est à l'usage exclusif de son destinataire. Toute
utilisation non autorisée peut être illicite. Si vous recevez ce
message par erreur, nous vous remercions d'en aviser immédiatement
l'expéditeur en utilisant la fonction réponse de votre gestionnaire
de courrier électronique."

"This email may contain confidential information and/or copyright
material. This email is intended for the use of the addressee only.
Any unauthorised use may be unlawful. If you receive this email by
mistake, please advise the sender immediately by using the reply
facility in your email software."
begin:vcard
fn:Olivier  Boissard
n:Boissard;Olivier 
org;quoted-printable:CERENE SERVICES;d=C3=A9veloppement
adr:;;3 rue archimede;La Chapelle Saint Luc;AUBE;10600;FRANCE
email;internet:olivier.boissard@xxxxxxxxx
tel;work:+33.3.25.74.11.78
tel;fax:+33.3.25.78.39.67
note;quoted-printable:"Ce message peut contenir des informations confidentielles et/ou=0D=0A=
	prot=C3=A9g=C3=A9es. Il est =C3=A0 l'usage exclusif de son destinataire.=
	 Toute=0D=0A=
	utilisation non autoris=C3=A9e peut =C3=AAtre illicite. Si vous recevez=
	 ce=0D=0A=
	message par erreur, nous vous remercions d'en aviser imm=C3=A9diatement=0D=0A=
	l'exp=C3=A9diteur en utilisant la fonction r=C3=A9ponse de votre gestionn=
	aire=0D=0A=
	de courrier =C3=A9lectronique."=0D=0A=
	=0D=0A=
	"This email may contain confidential information and/or copyright=0D=0A=
	material. This email is intended for the use of the addressee only.=0D=0A=
	Any unauthorised use may be unlawful. If you receive this email by=0D=0A=
	mistake, please advise the sender immediately by using the reply=0D=0A=
	facility in your email software."
url:www.cerene.fr
version:2.1
end:vcard

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux