Feedback-ID: i76984098:Fastmail
Message-ID: <5e7e85fc-f462-41aa-a239-0866a6f72f9b@aklaver.com>
Date: Sun, 8 Feb 2026 17:41:47 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: REFRESH MATERIALIZED VIEW CONCURRENTLY is blocking autovacuum on
 table
To: Dirk Krautschick <dee-kay@gmx.de>, pgsql-general@lists.postgresql.org
References: <918deb54-9d01-4a9c-abd3-d8412c9e6c80@gmx.de>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <918deb54-9d01-4a9c-abd3-d8412c9e6c80@gmx.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/5e7e85fc-f462-41aa-a239-0866a6f72f9b%40aklaver.com>
Precedence: bulk

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
adrian.klaver@aklaver.com