public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: Loading the latest N rows into the cache seems way too fast.
Date: Mon, 17 Feb 2025 18:03:18 -0500
Message-ID: <CANzqJaC=6pUTsveOdL=FS1vz_FGjMbZKuzJ27JxsPfNbYN2fUA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CANzqJaBTPgTJ_M3dGiOa5H-FvAo71oCCa1QHejbzK+joKdrSyw@mail.gmail.com>
<[email protected]>
<CANzqJaDPR_sshr1hXuMsiZQDf7nH4BthNioCHJ4cVcGKxiSg_Q@mail.gmail.com>
<[email protected]>
On Mon, Feb 17, 2025 at 4:51 PM Tom Lane <[email protected]> wrote:
> 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.)
>
That's definitely taking a LOT longer...
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
view thread (6+ messages)
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]
Subject: Re: Loading the latest N rows into the cache seems way too fast.
In-Reply-To: <CANzqJaC=6pUTsveOdL=FS1vz_FGjMbZKuzJ27JxsPfNbYN2fUA@mail.gmail.com>
* 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