Postgres Pro
Downloads
Home   >   mailing lists

Re: VACUUM vs VACUUM FULL (was: SELECT * FROM huge_table LIMIT 10; Why does it take more than 10 min to complete, with cold caches) - Mailing list pgsql-general

From Christophe Pettus
Subject Re: VACUUM vs VACUUM FULL (was: SELECT * FROM huge_table LIMIT 10; Why does it take more than 10 min to complete, with cold caches)
Date
Msg-id 01D1B408-EADC-41C7-A695-7C84F649F702@thebuild.com
Whole thread Raw
In response to Re: VACUUM vs VACUUM FULL (was: SELECT * FROM huge_table LIMIT 10; Why does it take more than 10 min to complete, with cold caches)  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: VACUUM vs VACUUM FULL (was: SELECT * FROM huge_table LIMIT 10; Why does it take more than 10 min to complete, with cold caches)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tree view 

> On Feb 1, 2023, at 10:45, David G. Johnston <david.g.johnston@gmail.com> wrote:
> The system just isn't that intelligent for "sequential scan", instead it does literally what the label says, goes
throughthe table one page at a time and returns any live rows it finds.  

Although this does raise a question: Couldn't it skip pages that are marked appropriately in the visibility map?

pgsql-general by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: VACUUM vs VACUUM FULL (was: SELECT * FROM huge_table LIMIT 10; Why does it take more than 10 min to complete, with cold caches)
Next
From: Kirk Wolak
Date:
Subject: Re: Sequence vs UUID