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

From Peter J. Holzer
Subject Re: does refreshing materialized view make the database bloat?
Date
Msg-id 20230114085133.7yzay2whq566lzds@hjp.at
Whole thread Raw
In response to does refreshing materialized view make the database bloat?  (jian he <jian.universality@gmail.com>)
List pgsql-general
On 2023-01-14 11:34:13 +0530, jian he 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? 

Tables are implemented as files by PostgreSQL. When a table is dropped,
the file is deleted[1]. Whether that means that the space is
"immediately" available again is up to the operating system.

        hp

[1] Possibly delayed until commit.

--
   _  | Peter J. Holzer    | Story must make more sense than reality.
|_|_) |                    |
| |   | hjp@hjp.at         |    -- Charles Stross, "Creative writing
__/   | http://www.hjp.at/ |       challenge!"

Attachment

pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: does refreshing materialized view make the database bloat?
Next
From: Tom Lane
Date:
Subject: Re: Why is a hash join preferred when it does not fit in work_mem