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 931647.1739828197@sss.pgh.pa.us
Whole thread Raw
In response to 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:
> 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.)

            regards, tom lane



pgsql-general by date:

Previous
From: Christoph Moench-Tegeder
Date:
Subject: Re: Loading the latest N rows into the cache seems way too fast.
Next
From: Ron Johnson
Date:
Subject: Re: Loading the latest N rows into the cache seems way too fast.