| From: | Seamus Abshere <seamus(at)abshere(dot)net> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Melvin Davidson <melvin6925(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Read-only tables to avoid row visibility check |
| Date: | 2016-02-22 22:33:50 |
| Message-ID: | 1456180430.1076080.528763098.3C548094@webmail.messagingengine.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Feb 22, 2016, at 06:48 PM, David G. Johnston wrote:
> it would probably be more constructive to actually communicate the thoughts that provoked the question.
My company has a largish table - 250+ columns, 1 row for every household
in the US. It's read-only. We've gotten advice to convert to a column
store (cstore_fdw, etc.) but we would love to just stay with
tried-and-true postgres tables. Plus, many of our queries are against
dozens of columns at once.
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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nicklas Aven | 2016-02-22 22:35:18 | Re: ERROR: cannot convert relation containing dropped columns to view |
| Previous Message | Tom Lane | 2016-02-22 22:21:53 | Re: ERROR: cannot convert relation containing dropped columns to view |