From: | aditya desai <admad123(at)gmail(dot)com> |
---|---|
To: | Michael Lewis <mlewis(at)entrata(dot)com> |
Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Query out of memory |
Date: | 2021-10-19 13:48:04 |
Message-ID: | CAN0SRDEFCMLu6Ue_zR0=okw2GZjCOoWXvdqE0d-idGb8DasWVg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance pgsql-sql |
Thanks Michael. I will check this further.
On Tue, Oct 19, 2021 at 7:09 PM Michael Lewis <mlewis(at)entrata(dot)com> wrote:
> Check explain plan, change work mem to 100MBs and then check explain plan
> again. If it changed, then try explain analyze.
>
> Work mem is limit is used per node in the plan, so especially with
> partitioned tables, that limit is way too high.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Mithran Kulasekaran | 2021-10-19 21:47:05 | Postgres views cannot use both union and join/where |
Previous Message | Michael Lewis | 2021-10-19 13:39:34 | Re: Query out of memory |
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2021-10-19 14:37:20 | Re: create a procedure based on column data change in postgrersql |
Previous Message | Jian He | 2021-10-19 13:45:50 | create a procedure based on column data change in postgrersql |