| From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Memory leak from ExecutorState context? |
| Date: | 2023-02-28 18:55:54 |
| Message-ID: | 40ea5c5d-2420-d85f-eb5b-23322df61c8d@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/28/23 19:25, Justin Pryzby wrote:
> On Tue, Feb 28, 2023 at 07:06:43PM +0100, Jehan-Guillaume de Rorthais wrote:
>> Hello all,
>>
>> A customer is facing out of memory query which looks similar to this situation:
>>
>> https://www.postgresql.org/message-id/flat/12064.1555298699%40sss.pgh.pa.us#eb519865575bbc549007878a5fb7219b
>>
>> This PostgreSQL version is 11.18. Some settings:
>
> hash joins could exceed work_mem until v13:
>
> |Allow hash aggregation to use disk storage for large aggregation result
> |sets (Jeff Davis)
> |
That's hash aggregate, not hash join.
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2023-02-28 19:02:42 | Re: Experiments with Postgres and SSL |
| Previous Message | Greg Stark | 2023-02-28 18:45:27 | Commitfest 2023-03 starting tomorrow! |