From: Антон Мазунин <mazuninanton@gmail.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Refresh materialized view vs recreate
Date: Tue, 1 Nov 2016 11:26:42 +0500
Message-ID: <D5A51BDB-2EA7-4200-8F10-EB6AA5541DAC@gmail.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Hello!
We have a situation when after creation of new materialized view cpu utilization falls down (from about 50% to about 30%), at the same time we have a cron job, which does refresh of old materialized view, but it does no effect at performance.
Can anyone explain why is it so? And what is the difference between refresh and create new?
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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-performance@postgresql.org
Cc: mazuninanton@gmail.com
Subject: Re: Refresh materialized view vs recreate
In-Reply-To: <D5A51BDB-2EA7-4200-8F10-EB6AA5541DAC@gmail.com>
* 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