Re: Loading the latest N rows into the cache seems way too fast. - Mailing list pgsql-general

From Tom Lane
Subject Re: Loading the latest N rows into the cache seems way too fast.
Date
Msg-id 933145.1739829070@sss.pgh.pa.us
Whole thread Raw
In response to Re: Loading the latest N rows into the cache seems way too fast.  (Ron Johnson <ronljohnsonjr@gmail.com>)
Responses Re: Loading the latest N rows into the cache seems way too fast.
List pgsql-general
Ron Johnson <ronljohnsonjr@gmail.com> writes:
> On Mon, Feb 17, 2025 at 4:36 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> It's not pulling in the TOAST storage where the bytea column lives.
>> (pg_prewarm wouldn't have either, without special pushups.)

> Puzzling, since I ran "PERFORM *".  What if I explicitly mentioned the
> bytea column's name?

You'd have to do something that actually used the column's value,
perhaps "md5(byteacol)" or such.  (The obvious candidate would be
length(), but I think that is optimized to not fetch or decompress
the whole value.)

            regards, tom lane



pgsql-general by date:

Previous
From: Ron Johnson
Date:
Subject: Re: Loading the latest N rows into the cache seems way too fast.
Next
From: "David G. Johnston"
Date:
Subject: Re: Loading the latest N rows into the cache seems way too fast.