public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: Ron Johnson <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: Loading the latest N rows into the cache seems way too fast.
Date: Mon, 17 Feb 2025 16:51:10 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <CANzqJaDPR_sshr1hXuMsiZQDf7nH4BthNioCHJ4cVcGKxiSg_Q@mail.gmail.com>
References: <CANzqJaBTPgTJ_M3dGiOa5H-FvAo71oCCa1QHejbzK+joKdrSyw@mail.gmail.com>
<[email protected]>
<CANzqJaDPR_sshr1hXuMsiZQDf7nH4BthNioCHJ4cVcGKxiSg_Q@mail.gmail.com>
Ron Johnson <[email protected]> writes:
> On Mon, Feb 17, 2025 at 4:36 PM Tom Lane <[email protected]> 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
view thread (6+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Loading the latest N rows into the cache seems way too fast.
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox