| 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-27 11:39:54 |
| Message-ID: | CAGB0_65WW2GRF9qRx112a+jVeWLPSw+tyGKeuu_eNp8x+e7AbA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmail(dot)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(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-27 11:51:56 | Re: Autovacuum endless loop in heap_page_prune()? |
| Previous Message | Christian Schröder | 2024-05-27 11:32:37 | Memory issues with PostgreSQL 15 |