Re: [EXT] Improve "select count(*)" query - takes more than 30 mins for some large tables - Mailing list pgsql-admin

From Ron
Subject Re: [EXT] Improve "select count(*)" query - takes more than 30 mins for some large tables
Date
Msg-id 3dc59390-b2ab-4ccb-3e3f-cc7a1c095829@gmail.com
Whole thread Raw
In response to Re: [EXT] Improve "select count(*)" query - takes more than 30 mins for some large tables  (Scott Ribe <scott_ribe@elevated-dev.com>)
List pgsql-admin
On 7/12/22 21:28, Scott Ribe wrote:
>> On Jul 12, 2022, at 8:12 PM, MichaelDBA <MichaelDBA@sqlexec.com> wrote:
>>
>> Oh really? Even if it did an INDEX ONLY SCAN, it would still be slower because it still has to access the heap in a
randomI/O kinda way  (like I said-->"The heap always gets accessed for select counts") because visibility info is only
foundin the HEAP not the index.
 
> This changed in 9.something. There is now a visibility map, which can, for data that hasn't changed recently,

How recently is "recently"?  And does VACUUM clean it up?

-- 
Angular momentum makes the world go 'round.



pgsql-admin by date:

Previous
From: Mladen Gogala
Date:
Subject: Re: [EXT] Re: Improve "select count(*)" query - takes more than 30 mins for some large tables
Next
From: Goti
Date:
Subject: Check Postgres DB open mode