Re: Feature: temporary materialized views - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Feature: temporary materialized views
Date
Msg-id 20181226170022.w2pmdkdbkj2fqbbx@alvherre.pgsql
Whole thread Raw
In response to Feature: temporary materialized views  (Mitar <mmitar@gmail.com>)
Responses Re: Feature: temporary materialized views  (Mitar <mmitar@gmail.com>)
Re: Feature: temporary materialized views  (Mitar <mmitar@gmail.com>)
List pgsql-hackers
On 2018-Dec-25, Mitar wrote:

> Sometimes materialized views are used to cache a complex query on
> which a client works. But after client disconnects, the materialized
> view could be deleted. Regular VIEWs and TABLEs both have support for
> temporary versions which get automatically dropped at the end of the
> session. It seems it is easy to add the same thing for materialized
> views as well. See attached PoC patch.

I think MVs that are dropped at session end are a sensible feature.  I
probably wouldn't go as far as allowing ON COMMIT actions, though, so
this much effort is the right amount.

I think if you really want to do this you should just use OptTemp, and
delete OptNoLog.  Of course, you need to add tests and patch the docs.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: reducing the footprint of ScanKeyword (was Re: Large writable variables)
Next
From: Mitar
Date:
Subject: Re: Feature: triggers on materialized views