Re: does refreshing materialized view make the database bloat?

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: jian he <jian(dot)universality(at)gmail(dot)com>
Cc: pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: does refreshing materialized view make the database bloat?
Date: 2023-01-16 05:43:41
Message-ID: CAKFQuwauJe7RmT9aW-W3EJwT3DKjzJ-iW=pQ-g8JnNeayRnhHw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sunday, January 15, 2023, jian he <jian(dot)universality(at)gmail(dot)com> wrote:

>
>
> In the following example, I cannot see bloat (via extension pgstattuple
> dead_tuple_count>0). Wondering where the bloat is.
>
> --------do the update.
> update tbt set a = 10 + a where a < 20;
> REFRESH MATERIALIZED view tbtmv;
> SELECT * FROM pgstattuple('tbtmv'); -----no dead tuples count.
>

You didn’t specify concurrently so the merge method you quoted is not being
used.

David J.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Robert Sjöblom 2023-01-16 08:30:01 glibc initdb options vs icu compatibility questions (PG15)
Previous Message jian he 2023-01-16 05:29:15 Re: does refreshing materialized view make the database bloat?