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 1sBYi2-00HRwa-Rm for pgsql-general@arkaria.postgresql.org; Mon, 27 May 2024 11:40:12 +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 1sBYi1-006PVB-Cd for pgsql-general@arkaria.postgresql.org; Mon, 27 May 2024 11:40:09 +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 1sBYi1-006PV3-1E for pgsql-general@lists.postgresql.org; Mon, 27 May 2024 11:40:09 +0000 Received: from mail-ua1-x92a.google.com ([2607:f8b0:4864:20::92a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sBYhy-0010kw-Jl for pgsql-general@lists.postgresql.org; Mon, 27 May 2024 11:40:08 +0000 Received: by mail-ua1-x92a.google.com with SMTP id a1e0cc1a2514c-80318a7e93dso1554498241.3 for ; Mon, 27 May 2024 04:40:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716810005; x=1717414805; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=GOUBSsC61wInibY+0w2FfEVNGAGxVxUUEDVlqxmg/U8=; b=b+DkaPtIeF2X8GU9sWVVVrGE2qREG+bVSa0w251QQdmTxllX796+jqOvXVDW6ujPbI 1T7iTArr8SwwqDFdIXWS7Sih5GErouUTx5ztujO/TSKHs8qg83WJKdVV21mygYUX2XhO uE2mDhyXdgP+9CzK1UhxL+d3FCMxzzu5f420ggvp1HW381NrOXtt3GLIX0jHxvONFU3O iVnToYYSRqED/EcAPZKsloOJfh9ndfgwobiDbZMDktUTSeThqP/crMcq/UnUht5U+7W8 UzZeTEvinLTqAXzOh/zM2yTdTcFAHnmeD2z5dldWBFMG2CH9MEMsd6xVeWvBsCY8F9wX AMjA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716810005; x=1717414805; h=cc: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=GOUBSsC61wInibY+0w2FfEVNGAGxVxUUEDVlqxmg/U8=; b=XVg7wT8JKKI2f9hUNLV5wcU8Etp7CnYEWUgKcWrSXxcBGt9AZaTBXqNNM1yJ2TbemR GosAUPSGVM5LPVfkiy5I154jrXYpmfaR8zlQJTIiYiVG5IkyeN1I50WnTCI2tj7RQby5 uUCUns10Uj7muCK/v9Kpo4PjghfnEZwcMKlQi9irBxO2lPBc0RMtQq8PCSgJDT+ywAgl 0rAamQ9rugAQ9IPJQSjpCWZgsKHLbS2221nNyAwFsfMAsQtQjjFMPdpm74eVtZhUI/+v Ua1weqvmBUjB11aYRwVQw+pHJPZK0NgxDPPW38acdyqO8r/BOhr8ttSLXUVm0ZN6VoYc WtEw== X-Forwarded-Encrypted: i=1; AJvYcCXZ42L+bNkKfVezaBGukuY6jdzW8G1lcb7lWPyLlm8rOrLr0PI8uX74KOuMI2Xjhe6bie84HmWHuDYHXGdqMwRssOxpX4Qm6GKnCDn4q0kcDGzG X-Gm-Message-State: AOJu0YwPy8+gT66ldnprdkBNtJK5tGnaSTe/Zhe8HxxSW2cAaFLkHlm+ Z8i2kfzmlM9gfGXNZ6T/ONqvFyfPXVVJy2ltk05yNM8sFJJF3esbxv23927KPe41WCzKiHZHhzQ X85sRq0q4kLEspDS+vbZgHRiKNBE= X-Google-Smtp-Source: AGHT+IHtu3T7axaTrS1QnQREqqtM6cKnbj/WloHPGbu0dqS4uYCBrUS2wUWpOSlN2yQQJx0U/C6dYh2YfFx7z+B5hHA= X-Received: by 2002:a05:6102:1172:b0:47b:b404:d63e with SMTP id ada2fe7eead31-48a385c9033mr7627105137.15.1716810005445; Mon, 27 May 2024 04:40:05 -0700 (PDT) MIME-Version: 1.0 References: <3901400.1716301132@sss.pgh.pa.us> In-Reply-To: From: =?UTF-8?B?U2HFoW8gR2FudGFy?= Date: Mon, 27 May 2024 13:39:54 +0200 Message-ID: Subject: Re: problem with query To: Tom Lane Cc: Laurenz Albe , David Rowley , pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000008588d606196dfa09" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000008588d606196dfa09 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable upgrade to "PostgreSQL 16.3 (Debian 16.3-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit" solved the problem regards, s On Wed, 22 May 2024 at 06:04, Sa=C5=A1o Gantar wrote: > ANALYZE pg_class; doesn't help > also, query is from "Hasura", so I don't have much room to maneuver > > On Tue, 21 May 2024 at 16:18, Tom Lane wrote: > >> =3D?UTF-8?B?U2HFoW8gR2FudGFy?=3D writes: >> > thanks for the info, but is there any solution, given that it's system >> > tables? >> >> Given the complexity of the query, I wonder if you're running into >> problems with join_collapse_limit/from_collapse_limit preventing >> the planner from considering all options. >> >> Also, as David already mentioned, ANALYZE on pg_class might help. >> >> regards, tom lane >> > --0000000000008588d606196dfa09 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
upgrade to "PostgreSQL 16.3 (Debian 16.3-1.pgdg120+1)= on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit&= quot;
solved the problem

regards,
s<= /div>

On Wed, 22 May 2024 at 06:04, Sa=C5=A1o Gantar <sasog23@gmail.com> wrote:
ANALYZE pg_class; doesn= 't help
also, query is from "Hasura", so I don't = have much room to maneuver

On Tue, 21 May 2024 at 16:18, Tom Lane <= tgl@sss.pgh.pa.us> wrote:
=3D= ?UTF-8?B?U2HFoW8gR2FudGFy?=3D <sasog23@gmail.com> writes:
> thanks for the info, but is there any solution, given that it's sy= stem
> tables?

Given the complexity of the query, I wonder if you're running into
problems with join_collapse_limit/from_collapse_limit preventing
the planner from considering all options.

Also, as David already mentioned, ANALYZE on pg_class might help.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 regards, tom lane
--0000000000008588d606196dfa09--