Re: Materialized views & dead tuples
| От | Wells Oliver |
|---|---|
| Тема | Re: Materialized views & dead tuples |
| Дата | |
| Msg-id | CAOC+FBUS6CX7QyJuqhtc94UC2Sg45a7kPxS-h=nDYEcUiLz7BA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Materialized views & dead tuples (Laurenz Albe <laurenz.albe@cybertec.at>) |
| Список | pgsql-admin |
Ah, thank you, most of these are CONCURRENTLY so this makes sense. Appreciate it.
On Wed, Jun 19, 2024 at 12:27 AM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Tue, 2024-06-18 at 15:28 -0700, Wells Oliver wrote:
> Apologies for the daft question, but I am surprised to see materialized views
> show up in pg_stat_user_tables with lots of dead tuples. These are rematerialized
> nightly and, I thought, this had the effect of replacing/recreating them anew.
> Can someone shed some light on this?
It makes a difference if you use REFRESH MATERIALIZED VIEW or
REFRESH MATERIALIZED VIEW CONCURRENTLY.
The first statement will just discard the materialized table and create it anew,
and you will never see a dead tuple.
The second statement executes the query and updates the materialized table, which
can lead to dead tuples just like a normal UPDATE or DELETE.
Yours,
Laurenz Albe
Wells Oliver
wells.oliver@gmail.com
wells.oliver@gmail.com
В списке pgsql-admin по дате отправления: