Re: Loading the latest N rows into the cache seems way too fast.
| От | Ron Johnson |
|---|---|
| Тема | Re: Loading the latest N rows into the cache seems way too fast. |
| Дата | |
| Msg-id | CANzqJaDPR_sshr1hXuMsiZQDf7nH4BthNioCHJ4cVcGKxiSg_Q@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Loading the latest N rows into the cache seems way too fast. (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Loading the latest N rows into the cache seems way too fast.
Re: Loading the latest N rows into the cache seems way too fast. |
| Список | pgsql-general |
On Mon, Feb 17, 2025 at 4:36 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
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.)
Puzzling, since I ran "PERFORM *". What if I explicitly mentioned the bytea column's name?
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
В списке pgsql-general по дате отправления: