materialised views vs unlogged table (also, ize vs ise)

From: Tim Kane <tim(dot)kane(at)gmail(dot)com>
To: pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: materialised views vs unlogged table (also, ize vs ise)
Date: 2014-05-18 21:47:49
Message-ID: CF9EE915.827F9%tim.kane@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

HI all,

I’m curious about materialised views.
I was just setting something up, and noticed there is no support for
UNLOGGED materialised views
(http://www.postgresql.org/message-id/E1UZNrD-0008Eh-83@gemulon.postgresql.o
rg)

I also notice that the creation of an unlogged table appears to be a lot
quicker than that of a materialised view (as you might expect).
Read operations seem indistinguishable, though I’ve not tested with cold
buffers.

Aside from the convenience of the REFRESH functionality, are there any other
factors I should consider?
(the base tables get dropped/recreated each night, so I can’t rely on
REFRESH functionality – I’ll need to recreate the table/view in either
case).

Oh, I also noticed we don’t support alternate spellings of MATERIALIZE, as
we do for ANALYZE.
I’m not sure if we do this anywhere else, maybe it’s just analyze being the
odd one out.

=# create materialized view testview as select 1;
SELECT 1
Time: 21.760 ms
=# create materialised view testview as select 1;
ERROR: syntax error at or near "materialised"
LINE 1: create materialised view testview as select 1;

Not that it isn’t difficult for users to simply spell it one way or the
other, it just seems a minor inconsistency.

Cheers,

Tim

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Varuna Seneviratna 2014-05-18 22:00:56 How to solve the problem "error reading c:\Program Files\PostgreSQL\9.3\data\postgresql.conf during installation"
Previous Message Raghavendra 2014-05-18 08:40:53 Is it typo in pg_stat_replication column name in PG 9.4 ?