Re: keeping an index in memory

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Rajarshi Guha" <rguha(at)indiana(dot)edu>
Cc: "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "pgsql-general" <pgsql-general(at)postgresql(dot)org>
Subject: Re: keeping an index in memory
Date: 2007-10-21 16:56:14
Message-ID: 87hckkwgnl.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Rajarshi Guha" <rguha(at)indiana(dot)edu> writes:

> The table itself is about 10M rows corresponding to 14GB.

Each row is on average 1.4kB ? Perhaps you should send more details of the
table definition and the typical size of each column. It's possible you have
the columns you're selecting on being stored out of line ("toasted") which
would hurt performance if you're often accessing many of those columns.

If it's not true then you may have a lot of dead space in your table which
would decrease performance.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Marlowe 2007-10-21 17:05:55 Re: keeping an index in memory
Previous Message Tom Lane 2007-10-21 15:39:06 Re: keeping an index in memory