Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxxxxxxxxx)

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux