Re: DB running out of memory issues after upgrade - Mailing list pgsql-general

From Merlin Moncure
Subject Re: DB running out of memory issues after upgrade
Date
Msg-id CAHyXU0zFXS214e4BtCPonbkiC60QQ2kWA8G2CXMhf0_q9ytAxg@mail.gmail.com
Whole thread Raw
In response to Re: DB running out of memory issues after upgrade  (Nagaraj Raj <nagaraj.sf@yahoo.com>)
List pgsql-general
On Tue, Feb 18, 2020 at 12:10 PM Nagaraj Raj <nagaraj.sf@yahoo.com> wrote:
>
> Below are the same configurations ins .conf file before and after updagrade
>
> show max_connections; = 1743
> show shared_buffers = "4057840kB"
> show effective_cache_size =  "8115688kB"
> show maintenance_work_mem = "259MB"
> show checkpoint_completion_target = "0.9"
> show wal_buffers = "16MB"
> show default_statistics_target = "100"
> show random_page_cost = "1.1"
> show effective_io_concurrency =" 200"
> show work_mem = "4MB"
> show min_wal_size = "256MB"
> show max_wal_size = "2GB"
> show max_worker_processes = "8"
> show max_parallel_workers_per_gather = "2"

This smells like oom killer for sure.  how did you resolve some of
these values.  In particular max_connections and effective_cache_size.
  How much memory is in this server?

merlin



pgsql-general by date:

Previous
From: Nagaraj Raj
Date:
Subject: Re: DB running out of memory issues after upgrade
Next
From: Anthony Hall
Date:
Subject: How to handle CASE statement with PostgreSQL without need for typecasting