From: Craig James <craig_james@emolecules.com>
To: pgsql-performance@postgresql.org
Subject: Re: Index containing records instead of pointers to the data?
Date: Sun, 18 Sep 2011 18:15:45 -0700
Message-ID: <4E7697C1.1080407@emolecules.com> (raw)
In-Reply-To: <CAFcOn2_SUv=C2CqOQn6_mjOLQ9f9eqsSG3JBE2S5dzbSWp_piw@mail.gmail.com>
References: <CAFcOn2_SUv=C2CqOQn6_mjOLQ9f9eqsSG3JBE2S5dzbSWp_piw@mail.gmail.com>
On 9/18/11 1:18 PM, Stefan Keller wrote:
> Hi,
>
> Sorry if this is an odd question:
> I assume that Postgres indexes don't store records but only pointers
> to the data.
> This means, that there is always an additional access needed (real table I/O).
> Would an index containing data records make sense?
See my post entitled, "How to make hash indexes fast" for a solution to the additional-disk-access problem.
Craig
>
> Stefan
>
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: Index containing records instead of pointers to the data?
In-Reply-To: <4E7697C1.1080407@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