| From: | Mitar <mmitar(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: CREATE UNLOGGED MATERIALIZED VIEW |
| Date: | 2018-12-25 18:29:05 |
| Message-ID: | CAKLmikNE81RcbzgBwioaHVCp0joz2WioPRLaw+tCw=MNWRD1mA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi!
On Tue, Dec 25, 2018 at 10:25 AM Adrian Klaver
<adrian(dot)klaver(at)aklaver(dot)com> wrote:
> Don't know. From my POV MATERIALIZED VIEWS are transient any way you
> look at them. They capture a state at a point in time and then the data
> they depend on moves on. Given that they can be refreshed at will not
> sure logging/not logging really matters.
I agree with you. But current default is RELPERSISTENCE_PERMANENT. So
there is an option for RELPERSISTENCE_UNLOGGED.
So, I think that we should or a) make RELPERSISTENCE_UNLOGGED default,
b) document RELPERSISTENCE_UNLOGGED or c) remove it.
I propose b).
Mitar
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-12-26 16:35:05 | Re: CREATE UNLOGGED MATERIALIZED VIEW |
| Previous Message | Adrian Klaver | 2018-12-25 18:25:23 | Re: CREATE UNLOGGED MATERIALIZED VIEW |