Seamus Abshere <sea...@abshere.net> writes:
> Being able to tell postgres that our table is "Read Only" has imaginary
> mystical properties for me, first and foremost being able to count
> against indexes without ever hitting the disk.
>> âIf the system is working properly then a READ ONLY table in fact should
>> be able to use Index Only Scans without the hack of a DBA telling it that
>> said table is READ ONLY.â
> So this should happen already?
Yeah. Index-only scans will work if all (or at least most) of the table
hasn't been modified since the last VACUUM. If we had a READ ONLY
property, I do not think it would affect that logic at all; it would just
prevent future mods going forward. Which, as noted, you could already do
by revoking suitable privileges.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
