Re: Loading the latest N rows into the cache seems way too fast.

2025-02-17 Thread Ron Johnson
On Mon, Feb 17, 2025 at 4:51 PM Tom Lane wrote: > Ron Johnson writes: > > On Mon, Feb 17, 2025 at 4:36 PM Tom Lane 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 "PERFOR

Re: Loading the latest N rows into the cache seems way too fast.

2025-02-17 Thread David G. Johnston
On Mon, Feb 17, 2025 at 2:41 PM Ron Johnson wrote: > On Mon, Feb 17, 2025 at 4:36 PM Tom Lane wrote: > >> Ron Johnson 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.

Re: Loading the latest N rows into the cache seems way too fast.

2025-02-17 Thread Tom Lane
Ron Johnson writes: > On Mon, Feb 17, 2025 at 4:36 PM Tom Lane 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 na

Re: Loading the latest N rows into the cache seems way too fast.

2025-02-17 Thread Ron Johnson
On Mon, Feb 17, 2025 at 4:36 PM Tom Lane wrote: > Ron Johnson 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 100K

Re: Loading the latest N rows into the cache seems way too fast.

2025-02-17 Thread Tom Lane
Ron Johnson 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

Re: Loading the latest N rows into the cache seems way too fast.

2025-02-17 Thread Christoph Moench-Tegeder
## Ron Johnson (ronljohnso...@gmail.com): > 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? > > $ time psql -h foo bar -Xc "DO

Loading the latest N rows into the cache seems way too fast.

2025-02-17 Thread Ron Johnson
PG 9.6.24 and PG 14.15, if it matters. (Yes, 9.6 is really EOL. I don't control that.) (I could use pg_prewarm, but the table is much bigger than RAM, and last_block value only has the newest record if data has never been deleted. The oldest records regularly get deleted, and then the table is v