Re: Read-only tables to avoid row visibility check

From: Melvin Davidson <melvin6925(at)gmail(dot)com>
To: Seamus Abshere <seamus(at)abshere(dot)net>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Read-only tables to avoid row visibility check
Date: 2016-02-22 21:30:57
Message-ID: CANu8Fiwu636Cg29YA8mcygeEWozO+TGav-eE6=ouurbA3GOCuA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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(at)abshere(dot)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(at)postgresql(dot)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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Seamus Abshere 2016-02-22 21:38:03 Re: Read-only tables to avoid row visibility check
Previous Message Nicklas Avén 2016-02-22 21:30:04 ERROR: cannot convert relation containing dropped columns to view