Re: index-only scans

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: index-only scans
Date: 2011-08-11 21:01:53
Message-ID: 4E444341.5070409@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 08/11/2011 01:57 PM, Greg Sabino Mullane wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
>
>> 1. The way that nodeIndexscan.c builds up the faux heap tuple is
>> perhaps susceptible to improvement. I thought about building a
>> virtual tuple, but then what do I do with an OID column, if I have
>> one? Or maybe this should be done some other way altogether.
>
> Maybe it's time to finally remove the been-deprecated-for-a-while OIDs?

As a user space option certainly. However they are also used to track
system objects, I don't know that we need to get rid of them for that
purpose. We just need to remove WITH/WITHOUT OIDS for user tables.

JD
--
Command Prompt, Inc. - http://www.commandprompt.com/
PostgreSQL Support, Training, Professional Services and Development
The PostgreSQL Conference - http://www.postgresqlconference.org/
@cmdpromptinc - @postgresconf - 509-416-6579

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-08-11 21:06:34 Re: index-only scans
Previous Message Greg Sabino Mullane 2011-08-11 20:57:39 Re: index-only scans