Re: does refreshing materialized view make the database bloat? - Mailing list pgsql-general

From David G. Johnston
Subject Re: does refreshing materialized view make the database bloat?
Date
Msg-id CAKFQuwaqHqvC7PgsmyxHQ00Hc0NhtaKB8aaKDsttsvRssKx27Q@mail.gmail.com
Whole thread Raw
In response to does refreshing materialized view make the database bloat?  (jian he <jian.universality@gmail.com>)
Responses Re: does refreshing materialized view make the database bloat?  (jian he <jian.universality@gmail.com>)
List pgsql-general
On Friday, January 13, 2023, jian he <jian.universality@gmail.com> wrote:

Once we have the diff table, we perform set-based DELETE and INSERT
operations against the materialized view, and discard both temporary tables.

Here the temporary tables are "discard" meaning the temporary tables are deleted and the temporary tables' spaces are reclaimed immediately?
Or the temporary tables are deleted and the spaces will be reclaimed by another mechanism? 

simplify:does refreshing materialized view make the database bloat.


The materialized view itself bloats.  The temp tables are removed immediately (the “drop table” docs don’t say this explicitly though it the most logical behavior and implied by the fact it takes an access exclusive lock).

David J.

pgsql-general by date:

Previous
From: Ken Tanzer
Date:
Subject: Re: Intervals and ISO 8601 duration
Next
From: "Peter J. Holzer"
Date:
Subject: Re: does refreshing materialized view make the database bloat?