From: | James(王旭) <wangxu(at)gu360(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: How to gracefully keep my specific index in memory ? |
Date: | 2019-08-13 03:42:37 |
Message-ID: | tencent_17D6E29A5E11CF007746933E@qq.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks Laurenz Albe for reply.
Unfortunately this index is only frequently used during a certain period of time(such as 9:30am - 12:00am) .I usually encounter slow load of this index during some other time.
Then it seems to me the only answer for this case would be the pgprewarm and pg_cron ?
------------------ Original ------------------
From: "Laurenz Albe"<laurenz(dot)albe(at)cybertec(dot)at>;
Date: Mon, Aug 12, 2019 08:24 PM
To: "James(王旭)"<wangxu(at)gu360(dot)com>; "pgsql-general"<pgsql-general(at)postgresql(dot)org>;
Subject: Re: How to gracefully keep my specific index in memory ?
James(王旭) wrote:
> As the title,How to keep a specific index in memory gracefully?
>
> After some statistical query, I can determine that not all indexes can be fit into memory,
> but one of the most frequently used indexes(say idx_xyz) can be definitely fit into
> memory(specifically ,[the size of idx_xyz]=20% x [memory size]).
>
> I know there's pgprewarm, but I feel with pgprewarm I can't keep things under control, e.g. no realtime monitor, being squeezed out of memory ,.etc.
>
> Is it possible that I can simply do something like "select idx_xyz into xxx" and keep the specific index in memory forever?
If the indexes are frequently used, they should remain cached anyway.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
From | Date | Subject | |
---|---|---|---|
Next Message | Shital A | 2019-08-13 06:20:21 | Re: Fwd: Postgres HA - pacemaker RA do not support auto failback |
Previous Message | Michael Paquier | 2019-08-13 03:10:09 | Re: question about client/server version mismatches |