From: Nagaraj Raj <nagaraj.sf@yahoo.com>
To: Justin Pryzby <pryzby@telsasoft.com>
To: Merlin Moncure <mmoncure@gmail.com>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Subject: Re: DB running out of memory issues after upgrade
Date: Tue, 18 Feb 2020 19:10:20 +0000 (UTC)
Message-ID: <1013528313.4707645.1582053020884@mail.yahoo.com> (raw)
In-Reply-To: <CAHyXU0yf0mUHH-mZUHKJ_LXzCsd5wfyjcPhiW_u2SVWvH=620w@mail.gmail.com>
References: <1425420656.4660607.1582047988379.ref@mail.yahoo.com>
<1425420656.4660607.1582047988379@mail.yahoo.com>
<20200218184037.GZ31889@telsasoft.com>
<CAHyXU0yf0mUHH-mZUHKJ_LXzCsd5wfyjcPhiW_u2SVWvH=620w@mail.gmail.com>
Hi Merlin,
Its configured high value for max_conn, but active and idle session have never crossed the count 50.
DB Size: 20 GBTable size: 30MBRAM: 16GBvC: 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)"
Thanks,Rj On Tuesday, February 18, 2020, 10:51:02 AM PST, Merlin Moncure <mmoncure@gmail.com> wrote:
On Tue, Feb 18, 2020 at 12:40 PM Justin Pryzby <pryzby@telsasoft.com> wrote:
> This is almost certainly unrelated. It looks like that query did a seq scan
> and accessed a large number of tuples (and pages from "shared_buffers"), which
> the OS then shows as part of that processes memory, even though *shared*
> buffers are not specific to that one process.
Yeah. This server looks highly overprovisioned, I'm in particularly
suspicious of the high max_connections setting. To fetch this out
I'd be tracking connections in the database, both idle and not idle,
continuously. The solution is most likely to install a connection
pooler such as pgbouncer.
merlin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: nagaraj.sf@yahoo.com, pryzby@telsasoft.com, mmoncure@gmail.com
Subject: Re: DB running out of memory issues after upgrade
In-Reply-To: <1013528313.4707645.1582053020884@mail.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox