| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Materialized views WIP patch |
| Date: | 2013-02-23 01:00:02 |
| Message-ID: | 51281492.6060501@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
> 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 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?
BTW, to contradict Peter E., for my part I would NOT want matview resets
to be logged as DDL. I would only want matview definitition changes to
be so logged.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-02-23 04:40:45 | pgsql: Add quotes to messages |
| Previous Message | Shigeru Hanada | 2013-02-22 22:43:19 | Re: pgsql: Add pg_xlogdump contrib program |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2013-02-23 01:55:23 | Re: Strange Windows problem, lock_timeout test request |
| Previous Message | Mike Toews | 2013-02-22 23:09:51 | Show type in psql SELECT |