Received: from localhost (unknown [200.46.204.183])
	by developer.postgresql.org (Postfix) with ESMTP id 3C36F2E008F
	for <pgsql-admin-postgresql.org@developer.postgresql.org>;
	Fri, 23 May 2008 10:27:52 -0300 (ADT)
Received: from developer.postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 53751-04-3
	for <pgsql-admin-postgresql.org@developer.postgresql.org>;
	Fri, 23 May 2008 10:27:38 -0300 (ADT)
X-Greylist: delayed 00:06:39.395901 by SQLgrey-1.7.6
Received: from web56411.mail.re3.yahoo.com (web56411.mail.re3.yahoo.com
	[216.252.111.90])
	by developer.postgresql.org (Postfix) with SMTP id 934B52E0066
	for <pgsql-admin@postgresql.org>; Fri, 23 May 2008 10:27:00 -0300 (ADT)
Received: (qmail 5953 invoked by uid 60001); 23 May 2008 13:20:19 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
	b=fbS5mhVtzlSljrngbnTw3SoMeMa1T8ykfBN7odb3BuOWmxGgK0FDXrO215cT0APZ6Eiv6YVPHcVlqfqeTCBBz+LvMXED0J7rqt+g9lcf5+O6AHvq0Q1nN+VdeEVwTFG+g+wkzM/i7htOd6NlhLJq3x8AXrVH0zPuhMBUqUOgf/M=;
Received: from [198.119.134.32] by web56411.mail.re3.yahoo.com via HTTP;
	Fri, 23 May 2008 06:20:19 PDT
X-Mailer: YahooMailRC/975.41 YahooMailWebService/0.7.199
Date: Fri, 23 May 2008 06:20:19 -0700 (PDT)
From: Jessica Richard <rjessil@yahoo.com>
Subject: index performance
To: pgsql-admin@postgresql.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1149724020-1211548819=:5203"
Message-ID: <501471.5203.qm@web56411.mail.re3.yahoo.com>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200805/196
X-Sequence-Number: 29280

--0-1149724020-1211548819=:5203
Content-Type: text/plain; charset=us-ascii

I have a large table with about 2 million rows and it will keep growing...

I need to do update/inserts, and select as well.

An index will speed up the select, but it will slow down the updates.

Are all Postgres indexes ordered? i.e., with every update, the index pages will have to be physically reordered?

Does Postgres have any kind of non-ordered indexes (like Syabse's non-clustered index)?

What is the common way to take care of the performance issue when you have to do both update and select on the same large table?

Thanks,
Jessica



      
--0-1149724020-1211548819=:5203
Content-Type: text/html; charset=us-ascii

<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div>I have a large table with about 2 million rows and it will keep growing...<br><br>I need to do update/inserts, and select as well.<br><br>An index will speed up the select, but it will slow down the updates.<br><br>Are all Postgres indexes ordered? i.e., with every update, the index pages will have to be physically reordered?<br><br>Does Postgres have any kind of non-ordered indexes (like Syabse's non-clustered index)?<br><br>What is the common way to take care of the performance issue when you have to do both update and select on the same large table?<br><br>Thanks,<br>Jessica<br></div></div><br>



      </body></html>
--0-1149724020-1211548819=:5203--