From: Thomas Kellerer <spam_eater@gmx.net>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Reading on how materialized views are materialized?
Date: Mon, 25 Jun 2018 08:23:43 +0200
Message-ID: <894dd06e-c708-bd3e-0a08-8b85e2dc27ff@gmx.net> (raw)
In-Reply-To: <CAOC+FBXZRGLGrwD3yh+XLW+869X5sdAEteOTQdNYy_omKSgptA@mail.gmail.com>
References: <CAOC+FBXZRGLGrwD3yh+XLW+869X5sdAEteOTQdNYy_omKSgptA@mail.gmail.com>
Wells Oliver schrieb am 22.06.2018 um 20:51:
> Where can I find some more detail? I am deciding between a flat table
> populated for the current month only with a script versus a
> materialized view, and I'd like to understand better if the latter is
> intelligently being refreshed (meaning years of data won't be
> re-populated, only what's changed).
MViews currently don't support "incremental" refresh in Postgres.
A refresh of a mview is essentially the same as:
truncate table foo;
insert into foo
select ...
from ....;
Where the SELECT part is the query used to define the mview.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: spam_eater@gmx.net, pgsql-admin@lists.postgresql.org
Subject: Re: Reading on how materialized views are materialized?
In-Reply-To: <894dd06e-c708-bd3e-0a08-8b85e2dc27ff@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox