public inbox for [email protected]  

help / color / mirror / Atom feed

From: Ron Johnson <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: Postgresql 16.3 Out Of Memory
Date: Mon, 3 Jun 2024 09:32:26 -0400
Message-ID: <CANzqJaArcMZs841VVvpOyrRfmOx5rnepwB9B-UgM4c=seTW5eA@mail.gmail.com> (raw)
In-Reply-To: <CAKAnmm+4RLHrKSyedZ+hTkwedP05+Ldp+bHiD00SuJvgAekRgA@mail.gmail.com>
References: <CAG4Txrii4-gTMpGEKLzCSe14svoJGgrh2AY=3LAgmqN2Um=o4A@mail.gmail.com>
	<CAKAnmm+4RLHrKSyedZ+hTkwedP05+Ldp+bHiD00SuJvgAekRgA@mail.gmail.com>

On Mon, Jun 3, 2024 at 9:12 AM Greg Sabino Mullane <[email protected]>
wrote:

> On Mon, Jun 3, 2024 at 6:19 AM Radu Radutiu <[email protected]> wrote:
>
>> Do you have any idea how to further debug the problem?
>>
>
> Putting aside the issue of non-reclaimed memory for now, can you show us
> the actual query? The explain analyze you provided shows it doing an awful
> lot of joins and then returning 14+ million rows to the client. Surely the
> client does not need that many rows?
>

And the query cost is really high.  "Did you ANALYZE the instance after
conversion?" was my first question.

reply

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: [email protected]
  Cc: [email protected]
  Subject: Re: Postgresql 16.3 Out Of Memory
  In-Reply-To: <CANzqJaArcMZs841VVvpOyrRfmOx5rnepwB9B-UgM4c=seTW5eA@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox