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)

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Dimitrios Apostolou <jimis(at)gmx(dot)net>, pgsql-general(at)lists(dot)postgresql(dot)org
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: 2023-02-01 18:47:17
Message-ID: 01D1B408-EADC-41C7-A695-7C84F649F702@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On Feb 1, 2023, at 10:45, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> The system just isn't that intelligent for "sequential scan", instead it does literally what the label says, goes through the 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?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kirk Wolak 2023-02-01 18:47:44 Re: Sequence vs UUID
Previous Message David G. Johnston 2023-02-01 18:45:48 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)