Re: Automatic aggressive vacuum on almost frozen table takes too long - Mailing list pgsql-general

From Peter Geoghegan
Subject Re: Automatic aggressive vacuum on almost frozen table takes too long
Date
Msg-id CAH2-Wzn5WkfsyxAKMhEcqV+BdTFy1AfNSztw8mA1WrPYWzHu8w@mail.gmail.com
Whole thread Raw
In response to Automatic aggressive vacuum on almost frozen table takes too long  (Mikhail Balayan <mv.balayan@gmail.com>)
Responses Re: Automatic aggressive vacuum on almost frozen table takes too long  (Mikhail Balayan <mv.balayan@gmail.com>)
List pgsql-general
On Thu, Feb 16, 2023 at 5:40 PM Mikhail Balayan <mv.balayan@gmail.com> wrote:
>> >> Do you have any non-btree indexes on the table? Can you show us the details of the
>> >> table, including all of its indexes? In other words, can you show "\d applications" output from psql?
>
> Only btree indexes. Please find the full table schema below:

It's possible that VACUUM had to wait a long time for a cleanup lock
on one individual heap page here, which could have added a long delay.
But...that doesn't seem particularly likely.

Can you run amcheck's bt_index_check() routine against some of the
indexes you've shown? There is perhaps some chance that index
corruption exists and causes VACUUM to take a very long time to delete
index pages. This is pretty much a wild guess, though.

-- 
Peter Geoghegan



pgsql-general by date:

Previous
From: Arthur Ramsey
Date:
Subject: Sequential scan faster than index
Next
From: Ryan MYJ
Date:
Subject: Hi All,