From: Craig James <craig_james@emolecules.com>
To: pgsql-performance@postgresql.org
Subject: Re: how fast index works?
Date: Tue, 06 Sep 2011 12:17:50 -0700
Message-ID: <4E6671DE.40506@emolecules.com> (raw)
In-Reply-To: <001501cc6cc3$3649a3c0$a2dceb40$@devshock.com>
References: <001501cc6cc3$3649a3c0$a2dceb40$@devshock.com>
On 9/6/11 11:31 AM, Anibal David Acosta wrote:
>
> Hi everyone,
>
> My question is, if I have a table with 500,000 rows, and a SELECT of one row is returned in 10 milliseconds, if the table has 6,000,000 of rows and everything is OK (statistics, vacuum etc)
>
> can i suppose that elapsed time will be near to 10?
>
Theoretically the index is a B-tree with log(N) performance, so a larger table could be slower. But in a real database, the entire subtree might fall together in one spot on the disk, so retrieving a record from a 500,000 record database could take the same time as a 6,000,000 record database.
On the other hand, if you do a lot of updates and don't have your autovacuum parameters set right, a 500,000 record index might get quite bloated and slow as it digs through several disk blocks to find one record.
There is no simple answer to your question. In a well-maintained database, 6,000,000 records are not a problem.
Craig
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: craig_james@emolecules.com
Subject: Re: how fast index works?
In-Reply-To: <4E6671DE.40506@emolecules.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