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

From Merlin Moncure
Subject Re: DB running out of memory issues after upgrade
Date
Msg-id CAHyXU0ziac57C5_TLr_MF+pFWAgKq=KbvUQuzUgiHk-zNt-OKg@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-performance
On Tue, Feb 18, 2020 at 1:10 PM Nagaraj Raj <nagaraj.sf@yahoo.com> wrote:
>
> Hi Merlin,
>
> Its configured high value for max_conn, but active and idle session have never crossed the count 50.
>
> DB Size: 20 GB
> Table size: 30MB
> RAM: 16GB
> vC: 4
>
>
> yes, its view earlier I posted and here is there query planner for new actual view,
>
> "Append  (cost=0.00..47979735.57 rows=3194327000 width=288)"
> "  ->  Seq Scan on msghist  (cost=0.00..15847101.30 rows=3162700000 width=288)"
> "  ->  Seq Scan on msghist msghist_1  (cost=0.00..189364.27 rows=31627000 width=288)"


Database size of 20GB is not believable; you have table with 3Bil
rows, this ought to be 60GB+ mill+ all by itself.   How did you get
20GB figure?


merlin



pgsql-performance by date:

Previous
From: Imre Samu
Date:
Subject: Re: PostgreSQL 11 higher Planning time on Partitioned table
Next
From: Ravi Garg
Date:
Subject: Re: PostgreSQL 11 higher Planning time on Partitioned table