public inbox for [email protected]
help / color / mirror / Atom feedFrom: David G. Johnston <[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 14:58:53 -0700
Message-ID: <CAKFQuwbLa1d4DMRQsYMzJ7OwcTCHYvuKcG7RD5meC0ryP_Za4g@mail.gmail.com> (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>
On Mon, Feb 17, 2025 at 2:41 PM Ron Johnson <[email protected]> wrote:
> On Mon, Feb 17, 2025 at 4:36 PM Tom Lane <[email protected]> wrote:
>
>> Ron Johnson <[email protected]> writes:
>> > The bigint "id" column in "mytbl" is populated from a sequence, and so
>> is
>> > monotonically increasing: the newest records will have the biggest id
>> > values.
>> > The table also has a bytea column that averages about 100KB.
>>
>> > Loading 200K rows is more than 200MB. I expected this "prewarm"
>> statement
>> > to take much longer than 1/2 second. Am I still in the dark ages of
>> > computer speed, or is this statement not doing what I hope it's doing?
>>
>> 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?
>
>
It's more about the system optimizing away data retrieval because you've
indicated you don't care about the contents due to using PERFORM. All it
needs is a pointer to represent the future data, not the data itself. And
PERFORM will never resolve that pointer by itself - so as Tom said your
query would need to force pointer resolution by computing on the data.
David J.
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: <CAKFQuwbLa1d4DMRQsYMzJ7OwcTCHYvuKcG7RD5meC0ryP_Za4g@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