| From: | Mitar <mmitar(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Feature: temporary materialized views |
| Date: | 2018-12-25 09:51:32 |
| Message-ID: | CAKLmikNoQR4ZNg_wt=-hU-uUxV2cXVdveeRsMFjr2SAopVxDxw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi!
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.
Mitar
| Attachment | Content-Type | Size |
|---|---|---|
| tempmatviews.patch | text/x-patch | 2.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | rajan | 2018-12-25 10:20:23 | Is there any way that one of the Postgres Background/Utility process may go down? |
| Previous Message | Fabien COELHO | 2018-12-25 09:32:34 | Re: pg_dumpall --exclude-database option |