| From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
|---|---|
| To: | Wei Shan <weishan(dot)ang(at)gmail(dot)com> |
| Cc: | "Sam R(dot)" <samruohola(at)yahoo(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: To keep indexes in memory, is large enough effective_cache_size enough? |
| Date: | 2018-09-20 05:17:25 |
| Message-ID: | CAKJS1f83CDUbv-vcOMpHj8=UfUpx7UTT2=9P_yj6H2BLEEKzOQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 20 September 2018 at 15:19, Wei Shan <weishan(dot)ang(at)gmail(dot)com> wrote:
> I believe you can use pg_prewarm to pin index or table to cache.
>
> https://www.postgresql.org/docs/current/static/pgprewarm.html
I think the key sentence in the document you linked to is:
"Prewarmed data also enjoys no special protection from cache
evictions, so it is possible that other system activity may evict the
newly prewarmed blocks shortly after they are read"
So this is not pinning. It's merely loading buffers into shared
buffers in the hope that they might be around long enough for you to
make the most of that effort.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladimir Ryabtsev | 2018-09-21 00:07:21 | Why could different data in a table be processed with different performance? |
| Previous Message | Wei Shan | 2018-09-20 03:19:43 | Re: To keep indexes in memory, is large enough effective_cache_size enough? |