| From: | Sašo Gantar <sasog23(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, David Rowley <dgrowleyml(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: problem with query |
| Date: | 2024-05-22 04:04:56 |
| Message-ID: | CAGB0_67P1JNuVXAijwXtET9YTpqWO=Uii=oeMb-KVaKXQCp=JQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> =?UTF-8?B?U2HFoW8gR2FudGFy?= <sasog23(at)gmail(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2024-05-22 07:29:16 | Re: Confusing error message in 15.6 |
| Previous Message | Dmitry O Litvintsev | 2024-05-21 23:58:42 | Re: Confusing error message in 15.6 |