From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
---|---|
To: | "Kevin Grittner" <kgrittn(at)mail(dot)com> |
Cc: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Pgsql Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Materialized views WIP patch |
Date: | 2012-11-27 14:20:30 |
Message-ID: | m2haobw2j5.fsf@2ndQuadrant.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Kevin Grittner" <kgrittn(at)mail(dot)com> writes:
> An ALTER MATERIALIZED VIEW option was my first thought on syntax to
> do what LOAD does in the current patch. But it bothered me that I
> couldn't think of any other cases where ALTER <some-object-type>
> only changed the data contained within the object and had no other
> impact. Are you both really comfortable with an ALTER MATERIALIZED
> VIEW which has no effect other than to update the data? It seems
> wrong to me.
I think you can already do that with some clever use of alter table ...
type using, or alter table set default.
> Sure -- a CONCURRENTLY option for LMV (or AMVU) seems like one of
> the next steps. I'll feel more confident about implementing that
> when it appears that we have shaken the last bugs out of
> CREATE/DROP INDEX CONCURRENTLY, since anything which affects those
> statements will probably also matter here.
Sure.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2012-11-27 14:41:37 | Re: Materialized views WIP patch |
Previous Message | David Johnston | 2012-11-27 14:17:14 | Re: Materialized views WIP patch |