| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Ayush Vatsa <ayushvatsa1810(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Jeremy Schneider <schneider(at)ardentperf(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Query regarding pg_prewarm extension |
| Date: | 2024-12-30 20:14:07 |
| Message-ID: | CAApHDvrWV2iekO7agpN2dEDi_F_QKwqQLwzqD8RR2jRC5DCgiQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 31 Dec 2024 at 06:24, Ayush Vatsa <ayushvatsa1810(at)gmail(dot)com> wrote:
> To me, using a range of pages to prewarm a relation doesn’t seem like a
> common use case. For example, if a user calls prewarm(100, 200),
> how would they decide those specific numbers? While it’s possible to
> inspect the contents of those pages, as Jeremy noted, users typically
> don’t track the location of specific rows for prewarming purposes.
It's probably rarely useful for that exact reason, however, for
insert-only tables (where only recently inserted data is queried),
which pages recently inserted rows are in is more predictable. I can
imagine that someone might want to load some recent percentage of the
table using these parameters.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2024-12-30 20:45:03 | Re: Statistics Import and Export |
| Previous Message | Jeff Davis | 2024-12-30 20:02:47 | Re: Statistics Import and Export |