| From: | Thom Brown <thom(at)linux(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)mail(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Materialized views WIP patch |
| Date: | 2012-11-16 17:04:43 |
| Message-ID: | CAA-aLv6pF=yrKqR85fp=2utvf5yLZNZhc6=Rf799SpMkhy+dRA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16 November 2012 16:25, Kevin Grittner <kgrittn(at)mail(dot)com> wrote:
> Josh Berkus wrote:
>
> > Unlogged is good.
>
> I agree that there are likely to be more use cases for this than
> temp MVs. Unfortunately, I've had a hard time figuring out how to
> flag an MV which is empty because its contents were lost after a
> crash with preventing people from using an MV which hasn't been
> populated, which has the potential to silently return incorrect
> results.
>
pg_class.relisvalid = false.. getting rid of the use for truncated MVs?
--
Thom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-11-16 17:05:17 | Re: another idea for changing global configuration settings from SQL |
| Previous Message | Robert Haas | 2012-11-16 17:02:05 | Re: Materialized views WIP patch |