Re: Postgresql 16.3 Out Of Memory

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Postgresql 16.3 Out Of Memory
Date: 2024-06-03 13:32:26
Message-ID: CANzqJaArcMZs841VVvpOyrRfmOx5rnepwB9B-UgM4c=seTW5eA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jun 3, 2024 at 9:12 AM Greg Sabino Mullane <htamfids(at)gmail(dot)com>
wrote:

> On Mon, Jun 3, 2024 at 6:19 AM Radu Radutiu <rradutiu(at)gmail(dot)com> 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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Victor Yegorov 2024-06-03 14:41:38 Unexpected results from CALL and AUTOCOMMIT=off
Previous Message Greg Sabino Mullane 2024-06-03 13:12:13 Re: Postgresql 16.3 Out Of Memory