public inbox for [email protected]  
help / color / mirror / Atom feed
REFRESH MATERIALIZED VIEW CONCURRENTLY is blocking autovacuum on table
3+ messages / 3 participants
[nested] [flat]

* REFRESH MATERIALIZED VIEW CONCURRENTLY is blocking autovacuum on table
@ 2026-02-09 01:17 Dirk Krautschick <[email protected]>
  2026-02-09 01:41 ` Re: REFRESH MATERIALIZED VIEW CONCURRENTLY is blocking autovacuum on table Adrian Klaver <[email protected]>
  2026-02-09 11:11 ` Re: REFRESH MATERIALIZED VIEW CONCURRENTLY is blocking autovacuum on table Laurenz Albe <[email protected]>
  0 siblings, 2 replies; 3+ messages in thread

From: Dirk Krautschick @ 2026-02-09 01:17 UTC (permalink / raw)
  To: [email protected]

Hi,

I have a situation here where a frequent

REFRESH MATERIALIZED VIEW CONCURRENTLY

is preventing autovacuum on some tables kind of running into a circle of 
growing.

Why is this acutally blocking autovacuum and what is the best practice 
to prevent
this excelt just not refreshing the materialized view frequently? :-)

Cheers

Dirk


^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: REFRESH MATERIALIZED VIEW CONCURRENTLY is blocking autovacuum on table
  2026-02-09 01:17 REFRESH MATERIALIZED VIEW CONCURRENTLY is blocking autovacuum on table Dirk Krautschick <[email protected]>
@ 2026-02-09 01:41 ` Adrian Klaver <[email protected]>
  1 sibling, 0 replies; 3+ messages in thread

From: Adrian Klaver @ 2026-02-09 01:41 UTC (permalink / raw)
  To: Dirk Krautschick <[email protected]>; [email protected]

On 2/8/26 17:17, Dirk Krautschick wrote:
> Hi,
> 
> I have a situation here where a frequent
> 
> REFRESH MATERIALIZED VIEW CONCURRENTLY
> 
> is preventing autovacuum on some tables kind of running into a circle of 
> growing.

You will need to:

1) Show the original CREATE MATERIALIZED VIEW command.

2) Indicate if the blocked autovacuum is on the tables the view is 
pulling from or other tables.

3) Tell us the Postgres version and whether it is community version or a 
fork.

> 
> Why is this acutally blocking autovacuum and what is the best practice 
> to prevent
> this excelt just not refreshing the materialized view frequently? :-)
> 
> Cheers
> 
> Dirk


-- 
Adrian Klaver
[email protected]






^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: REFRESH MATERIALIZED VIEW CONCURRENTLY is blocking autovacuum on table
  2026-02-09 01:17 REFRESH MATERIALIZED VIEW CONCURRENTLY is blocking autovacuum on table Dirk Krautschick <[email protected]>
@ 2026-02-09 11:11 ` Laurenz Albe <[email protected]>
  1 sibling, 0 replies; 3+ messages in thread

From: Laurenz Albe @ 2026-02-09 11:11 UTC (permalink / raw)
  To: Dirk Krautschick <[email protected]>; [email protected]

On Mon, 2026-02-09 at 02:17 +0100, Dirk Krautschick wrote:
> I have a situation here where a frequent 
> 
>  REFRESH MATERIALIZED VIEW CONCURRENTLY
> 
> is preventing autovacuum on some tables kind of running into a circle of growing.

I'm not sure I understand you correctly.

REFRESH MATERIALIZED VIEW CONCURRENTLY will block VACUUM on the materialized
view, because the statements take conflicting locks.

But the statement won't block VACUUM on the underlying tables.
However, if REFRESH MATERIALIZED VIEW CONCURRENTLY is running for a long time,
you will have a long-running transaction, and VACUUM won't be able to clean
up tuples that became dead later.

> Why is this acutally blocking autovacuum and what is the best practice to prevent 
> this excelt just not refreshing the materialized view frequently? :-)

I also have trouble understanding that sentence.

Yours,
Laurenz Albe






^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2026-02-09 11:11 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-02-09 01:17 REFRESH MATERIALIZED VIEW CONCURRENTLY is blocking autovacuum on table Dirk Krautschick <[email protected]>
2026-02-09 01:41 ` Adrian Klaver <[email protected]>
2026-02-09 11:11 ` Laurenz Albe <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox