Re: Loading the latest N rows into the cache seems way too fast.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Loading the latest N rows into the cache seems way too fast.
Date: 2025-02-17 21:51:10
Message-ID: 933145.1739829070@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ron Johnson <ronljohnsonjr(at)gmail(dot)com> writes:
> On Mon, Feb 17, 2025 at 4:36 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David G. Johnston 2025-02-17 21:58:53 Re: Loading the latest N rows into the cache seems way too fast.
Previous Message Ayush Vatsa 2025-02-17 21:45:30 Re: Clarification on Role Access Rights to Table Indexes