Re: Read-only tables to avoid row visibility check - Mailing list pgsql-general

From Tom Lane
Subject Re: Read-only tables to avoid row visibility check
Date
Msg-id 22147.1456181128@sss.pgh.pa.us
Whole thread Raw
In response to Re: Read-only tables to avoid row visibility check  (Seamus Abshere <seamus@abshere.net>)
List pgsql-general
Seamus Abshere <seamus@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
hackof 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


pgsql-general by date:

Previous
From: Melvin Davidson
Date:
Subject: Re: Get the date of creation of objects in the database
Next
From: "Edson F. Lidorio"
Date:
Subject: Re: Get the date of creation of objects in the database