Re: index-only scans - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: index-only scans
Date
Msg-id 638f6a3b0d5b5e25c0f493d0c0e1664c@biglumber.com
Whole thread Raw
In response to Re: index-only scans  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: index-only scans
Re: index-only scans
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160


>> Maybe it's time to finally remove the been-deprecated-for-a-while OIDs?

> I thought about just not supporting that for index-only scans, but
> system catalogs use them pretty extensively, and it doesn't seem out
> of the question that that could matter to people who have lots of SQL
> objects floating around.

Right - when I said remove, I meant for all but system catalogs. I 
would think those are generally small enough that for most people 
the lack of index-only scans on those would not matter. Heck, the 
system catalogs are already "special" in lots of ways other than 
having OIDs (most anyway), so it's not as though we'd be breaking 
sacred ground with an index-only exception. :)

I guess the question that should be asked is "we are going to finally 
remove OIDs someday, right?". If so, and if it's potentially blocking a 
major new feature, why not now?

- -- 
Greg Sabino Mullane greg@turnstep.com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201108112140
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAk5EhYEACgkQvJuQZxSWSsjnYQCgne81uKjiABVU3X3X+5cM/oFx
74YAoNX97hsOIxBx4Y1hcQHf/bWR813U
=hEl2
-----END PGP SIGNATURE-----




pgsql-hackers by date:

Previous
From: Cédric Villemain
Date:
Subject: Re: index-only scans
Next
From: Andrew Dunstan
Date:
Subject: Re: index-only scans