From: | Rajiv Ranjan <rajiv(dot)mca08(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Database Cache Hit Ratio (Warning) |
Date: | 2020-04-03 12:16:33 |
Message-ID: | CAKeFoKtYzfq+SyAcchcmcZMDmyFhWWyiFWYAMYidqp5sLmoS8w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Does this unnamed monitoring tool (and undefined query) really think higher
percentages are worse or are you mis-communicating?
Forget about the tool used for monitoring, important is to monitor the
"Cache hit ratio" is good or we can ignore it?
On Wed, 1 Apr 2020 at 10:44, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Tuesday, March 31, 2020, Rajiv Ranjan <rajiv(dot)mca08(at)gmail(dot)com> wrote:
>
>> Hi,
>>
>> Received a Database cache hit ratio warning alert from one of the
>> monitoring tools, the threshold for the “database cache hit ratio %” is
>> 90% for a High and 95% for Critical
>>
>
> Does this unnamed monitoring tool (and undefined query) really think
> higher percentages are worse or are you mis-communicating?
>
> David J.
>
--
*Thanks,*
*Rajiv Ranjan *
From | Date | Subject | |
---|---|---|---|
Next Message | Moses Mafusire | 2020-04-03 12:53:50 | Re: Cstore_fdw issue. |
Previous Message | Pavel Stehule | 2020-04-03 11:50:53 | Re: Out of memory in big transactions after upgrade to 12.2 |