BUG #16314: Database Cache Hit Ratio (Warning)

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: rajiv(dot)mca08(at)gmail(dot)com
Subject: BUG #16314: Database Cache Hit Ratio (Warning)
Date: 2020-03-24 12:06:01
Message-ID: 16314-451e54136ca0556d@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 16314
Logged by: Rajiv Ranjan
Email address: rajiv(dot)mca08(at)gmail(dot)com
PostgreSQL version: 9.6.0
Operating system: Red Hat Enterprise Linux Server release 7.6 (Maip)
Description:

Hi,

Currently, we are receiving a warning "Database Cache Hit Ratio
(%)(Warning)" from one of the monitoring tools.

We use Postgres database for Jira, confluence, and bitbucket application and
hosted on a different machine and only 35% disc space is used.

Database warning “Database Cache Hit Ratio” issue has been fixed by
increasing the below values however after a few days of stability the
warning is back hence not sure increasing the below parameters are correct
or not.

shared_buffers = 2GB
effective_cache_size = 6GB
maintenance_work_mem = 512MB

Could you please suggest how much we can increase the parameters and how
does it impact the database.

Thanks,
Rajiv Ranjan

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Fan Liu 2020-03-24 12:06:35 why wal_max_size does not work?
Previous Message postgres 2020-03-24 06:26:08 handle tablespaces for partitioned tables during ALTER DATABASE