Re: Materialized views WIP patch - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Materialized views WIP patch
Date
Msg-id CA+TgmoaNEZuXf54xKnbjJdjwg0TWNfhyhedo_CWMuR+Px4EvPg@mail.gmail.com
Whole thread Raw
In response to Re: Materialized views WIP patch  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Feb 28, 2013 at 11:00 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Well, personally, I'm in favor of either TRUNCATE or ALTER
>> MATERIALIZED VIEW ... DISCARD.  I think it's a dangerous precedent to
>> suppose that we're going to start using DISCARD for things that have
>> nothing to do with the existing meanings of DISCARD.
>
> Yeah, there's actually a serious problem with choosing DISCARD:
> surely we are not going to include "trash all MVs" in the behavior
> of DISCARD ALL.  So unless you would like to say that DISCARD ALL
> doesn't mean what it appears to mean, we can't make MV reset be
> one of the sub-flavors of DISCARD.

Good point.

> So that seems to leave us with either TRUNCATE or an ALTER sub-syntax.
> Personally I'd prefer the latter but it's surely debatable.

I agree.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Building on MinGW
Next
From: Alvaro Herrera
Date:
Subject: Re: sql_drop Event Trigger