public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tobias McNulty <[email protected]>
To: Greg Sabino Mullane <[email protected]>
Cc: [email protected]
Subject: Re: documentation question regarding REFRESH MATERIALIZED VIEW CONCURRENTLY
Date: Sun, 23 Feb 2025 10:34:25 -0500
Message-ID: <CAMGFDKQbLxahN8mthNU47r8iRB67261SQdk+BtbiBuOqtXNrUg@mail.gmail.com> (raw)
In-Reply-To: <CAKAnmm+14y_3HyHOcZwcHkqAvmZedXLSm97uVZHVr8eWg__W+Q@mail.gmail.com>
References: <CAMGFDKTW+SgLgdqRNa4cx9x1rFbA=2_8SE51r30A8o+9N2ikpA@mail.gmail.com>
<CAKAnmm+14y_3HyHOcZwcHkqAvmZedXLSm97uVZHVr8eWg__W+Q@mail.gmail.com>
On Sun, Feb 23, 2025 at 10:21 AM Greg Sabino Mullane <[email protected]> wrote:
> This is the correct interpretation. A regular refresh simply runs the query and replaces the old view, regardless of the number of rows that have changed. A concurrent refresh runs the query and updates the rows in place, so it is very sensitive as to how many of those rows have changed. This also means that many concurrent refreshes can lead to table bloat. And it will generate more WAL than a regular refresh.
>
> My takeaway: use regular refresh when you can. Switch to concurrent if the number of changes is very small, or if constant client access to the view is very important.
This makes sense to me. Many thanks.
Cheers,
Tobias
view thread (2+ messages)
reply
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: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: documentation question regarding REFRESH MATERIALIZED VIEW CONCURRENTLY
In-Reply-To: <CAMGFDKQbLxahN8mthNU47r8iRB67261SQdk+BtbiBuOqtXNrUg@mail.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 agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox