Re: Materialized views WIP patch

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Greg Stark <stark(at)mit(dot)edu>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Materialized views WIP patch
Date: 2013-02-23 13:00:14
Message-ID: CAB7nPqQyhwMHeDExqKy03N7=XbGEcS0GQrdZPtNkeDPSje4PPQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Sat, Feb 23, 2013 at 9:55 PM, Greg Stark <stark(at)mit(dot)edu> wrote:

> On Sat, Feb 23, 2013 at 1:00 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> > I prefer RESET, especially since it could eventually support RESET ALL
> > MATERIALIZED VIEWS if that turns out to be useful. How does the parser
> > like that?
>
> Isn't reset currently only used for GUCs? I think that makes for a
> strange crossover.
>
it is. http://www.postgresql.org/docs/9.2/static/sql-reset.html
DISCARD would be better.
My 2c.
--
Michael

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2013-02-23 17:21:06 pgsql: Rename postgres_fdw's use_remote_explain option to use_remote_es
Previous Message Greg Stark 2013-02-23 12:55:29 Re: Materialized views WIP patch

Browse pgsql-hackers by date

  From Date Subject
Next Message Stefan Andreatta 2013-02-23 13:11:16 Re: autoanalyze criteria
Previous Message Greg Stark 2013-02-23 12:55:29 Re: Materialized views WIP patch