Postgres Pro
Downloads
Home   >   mailing lists

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

From Melvin Davidson
Subject Re: Read-only tables to avoid row visibility check
Date
Msg-id CANu8Fiwu636Cg29YA8mcygeEWozO+TGav-eE6=ouurbA3GOCuA@mail.gmail.com
Whole thread Raw
In response to Read-only tables to avoid row visibility check  (Seamus Abshere <seamus@abshere.net>)
Responses Re: Read-only tables to avoid row visibility check  (Seamus Abshere <seamus@abshere.net>)
List pgsql-general
Tree view
First of all, it would be really nice if you mentioned the version of PostgreSQL and O/S when posing questions.

That being said, that wiki is a _discussion_, and as such, a suggestion on how it "might" be implemented.

However, at this time, there is no such option as SET READ ONLY in any version of PostgreSQL.

The best you can do is revoke INSERT, UPDATE & DELETE from public and all specific granted users.

On Mon, Feb 22, 2016 at 3:35 PM, Seamus Abshere <seamus@abshere.net> wrote:
hi,

https://wiki.postgresql.org/wiki/ReadOnlyTables mentions the possibility
of `ALTER TABLE table SET READ ONLY`.

Would this mean that row visibility checks could be skipped and thus
index-only scans much more common?

Thanks,
Seamus

--
Seamus Abshere, SCEA
+598 99 54 99 54
https://github.com/seamusabshere


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



--
Melvin Davidson
I reserve the right to fantasize.  Whether or not you
wish to share my fantasy is entirely up to you.

pgsql-general by date:

Previous
From: Nicklas Avén
Date:
Subject: ERROR: cannot convert relation containing dropped columns to view
Next
From: Seamus Abshere
Date:
Subject: Re: Read-only tables to avoid row visibility check