From: Jessica Richard <rjessil@yahoo.com>
To: pgsql-performance@postgresql.org
Subject: index performance on large tables with update and insert
Date: Fri, 23 May 2008 06:21:17 -0700 (PDT)
Message-ID: <334290.54805.qm@web56401.mail.re3.yahoo.com> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: rjessil@yahoo.com
Subject: Re: index performance on large tables with update and insert
In-Reply-To: <334290.54805.qm@web56401.mail.re3.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox