Re: problem with query
| От | Sašo Gantar |
|---|---|
| Тема | Re: problem with query |
| Дата | |
| Msg-id | CAGB0_65WW2GRF9qRx112a+jVeWLPSw+tyGKeuu_eNp8x+e7AbA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: problem with query (Sašo Gantar <sasog23@gmail.com>) |
| Список | pgsql-general |
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šo Gantar <sasog23@gmail.com> wrote:
ANALYZE pg_class; doesn't helpalso, query is from "Hasura", so I don't have much room to maneuverOn Tue, 21 May 2024 at 16:18, Tom Lane <tgl@sss.pgh.pa.us> wrote:Sašo Gantar <sasog23@gmail.com> 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
В списке pgsql-general по дате отправления: