Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sE7nm-00HMWx-A0 for pgsql-general@arkaria.postgresql.org; Mon, 03 Jun 2024 13:32:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sE7nm-00AZvZ-DE for pgsql-general@arkaria.postgresql.org; Mon, 03 Jun 2024 13:32:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sE7nm-00AZvQ-28 for pgsql-general@lists.postgresql.org; Mon, 03 Jun 2024 13:32:42 +0000 Received: from mail-oa1-x30.google.com ([2001:4860:4864:20::30]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sE7nj-0028PG-6E for pgsql-general@postgresql.org; Mon, 03 Jun 2024 13:32:41 +0000 Received: by mail-oa1-x30.google.com with SMTP id 586e51a60fabf-250aa4e8306so954362fac.0 for ; Mon, 03 Jun 2024 06:32:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717421557; x=1718026357; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=WfHQ6Xxe6TQzeFe2gGrVddTEC+Y+ferOghado7Hw91Y=; b=hFTTDMR2Qltk5ZRhBM1lE8uiMrGp3zqfeKFM6pStXNmTTvlS0yCjuvi0X2KupT5DK4 zOYK3r/P0pK/FITi4Q5N1yP5m8EFomAxGQE9X+05vq3pkHULe2Ok6dFmNySMK3qwamvE j+kOvNsy9CO8/N8vcEjqqpNqMavu4kCN3GluQV2tLIXEX7JhNVEZdcQgDDmT26ZMhOmP sI8ALi4ydaXxEGDNzIt1j9QZp9UFFtv7EfSwZtL48jFIpcnYnUDJWx2bnCaAKMZntd7c +aAFzunpUAXnj0K8tv1QMQWC/CzpuPTEjLwj6OMB1DrUgKSdRXwggpLY32ubC78/dbEV heow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717421557; x=1718026357; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=WfHQ6Xxe6TQzeFe2gGrVddTEC+Y+ferOghado7Hw91Y=; b=oyk12C3+De9uSMudQbYXr/MAmkbprgZxzT1PwJUBatjQGuLFquxX5f5LMIiS7c1bFn BBbr6BkVA96p16/OgMGeYVJ3FIrlhJ5eRtxoZmp9JV52Yrxm33bLN7lrrSu3dEcUhufW pksjw+iLpTVQRp57TGimfA0nytEGd9eDE3UtbcBWBJTxP4SIJGwAZ/M8uk7eQKknztaR UBIoUAogi2roAXssMDimpgV+q5Aqgpp1Z5CFeUUwyajVMgjofsGxyKIdpQ56q7q+O+kR /oll/gr3v3h4fW0YmoXHh/bkkLbu48uqPdt0lF7PBMpEAhov12aBPy76nWZbqV8PHcyN /NHg== X-Gm-Message-State: AOJu0Yz+TpeopItVkJoL9rS2bxJ3MW9QZD3Y45TdbeK9an60COR9vIrN rb5IvOR58PkLc6UsZWEP9mRDlA7lFyhnE8pfFxX4D6vtUFblToze/WmKdXUtMDffnUGV2o9LdhM maCv91x7nLqsQNEYSlvJwFnfRJGm1Ug== X-Google-Smtp-Source: AGHT+IHVoGoGv6O43z0hqN59+83PEdsZOkegrE4coDj3v/4BJYOiP5uN+DIs+Pu7A6d/R+73HFawmqWqGHHsatBegys= X-Received: by 2002:a05:6870:9a11:b0:21f:1705:d5b0 with SMTP id 586e51a60fabf-2508bb80660mr11249366fac.52.1717421557120; Mon, 03 Jun 2024 06:32:37 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Mon, 3 Jun 2024 09:32:26 -0400 Message-ID: Subject: Re: Postgresql 16.3 Out Of Memory To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000d78ca90619fc5d10" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d78ca90619fc5d10 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Jun 3, 2024 at 9:12=E2=80=AFAM Greg Sabino Mullane wrote: > On Mon, Jun 3, 2024 at 6:19=E2=80=AFAM Radu Radutiu = 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 awfu= l > lot of joins and then returning 14+ million rows to the client. Surely th= e > 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. --000000000000d78ca90619fc5d10 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Jun 3, 2024 at 9:12=E2=80=AFAM Gr= eg Sabino Mullane <htamfids@gmail.= com> wrote:
On Mon, Jun= 3, 2024 at 6:19=E2=80=AFAM Radu Radutiu <rradutiu@gmail.com> wrote:=C2=A0
=
Do you have any idea how to further debug the probl= em?=C2=A0

Putting aside the iss= ue of non-reclaimed memory for now, can you show us the actual query? The e= xplain analyze you provided shows it doing an awful lot of joins and then r= eturning 14+ million rows to the client. Surely the client does not need th= at many rows?

And the que= ry cost is really high.=C2=A0 "Did you ANALYZE the instance after conv= ersion?" was my first question.
--000000000000d78ca90619fc5d10--