Re: Autovacuum log messges re: index scans

From: vignesh kumar <vigneshkumar(dot)venugopal(at)outlook(dot)com>
To: Wells Oliver <wells(dot)oliver(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Autovacuum log messges re: index scans
Date: 2024-06-04 01:47:29
Message-ID: MN0PR20MB491294A3555B1F37AB739D2C87F82@MN0PR20MB4912.namprd20.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

So which means your postgres is working as expected, autovaccum has identified some reusable pages where it can fit in data just to reclaim the free ones..

Dead ones are just hanging around in your page writing or holding nothing.

Get Outlook for Android<https://aka.ms/AAb9ysg>
________________________________
From: Wells Oliver <wells(dot)oliver(at)gmail(dot)com>
Sent: Tuesday, May 14, 2024 6:19:33 AM
To: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Autovacuum log messges re: index scans

Can someone point me to more detail about this sort of message which comes from the automatic vacuum log messages?

index scan needed: 309538 pages from table (17.70% of total) had 27187607 dead item identifiers removed

I am trying to figure out what the "dead item identifiers" means exactly and what's happening here in this step. Does it indicate an index was somehow optimized?

I do see lines following this that pertain to individual indexes, what can I glean exactly from these? e.g.

index "myidx": pages: 169980 in total, 9410 newly deleted, 9681 currently deleted, 271 reusable

Thank you.

--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com<mailto:wellsoliver(at)gmail(dot)com>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Naveed Iftikhar 2024-06-04 02:23:15 pgBackRest configuration with DDBoost
Previous Message vignesh kumar 2024-06-04 01:41:56 Re: Upgrade from PostgreSQL version 10 to 16