| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Marko Tiikkaja <pgmail(at)joh(dot)to>, Greg Stark <stark(at)mit(dot)edu>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Materialized views WIP patch |
| Date: | 2013-02-21 15:42:00 |
| Message-ID: | 26479.1361461320@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Kevin Grittner <kgrittn(at)ymail(dot)com> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Peter claimed upthread that REFRESH is a subcommand of ALTER
>> MATERIALIZE VIEW
> It's not, nor do I think it should be.
Oh, never mind then.
>> and that this operation should be another one. That sounds
>> pretty reasonable from here.
> That feels completely wrong to me. For one thing, I can't think of
> any ALTER commands to populate or remove data. What did you think
> of the idea of something like DISCARD MATERIALIZED VIEW DATA as a
> new statment? Or maybe RESET MATERIALIZED VIEW?
I could live with either DISCARD or RESET.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-02-21 21:48:07 | Re: Materialized views WIP patch |
| Previous Message | Kevin Grittner | 2013-02-21 15:35:58 | Re: Materialized views WIP patch |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2013-02-21 15:51:18 | Re: JSON Function Bike Shedding |
| Previous Message | Albe Laurenz | 2013-02-21 15:36:02 | Re: FDW for PostgreSQL |