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
- Re: Memory leak from ExecutorState context? Justin Pryzby
- Re: Memory leak from ExecutorState contex... Tomas Vondra
- Re: Memory leak from ExecutorState contex... Jehan-Guillaume de Rorthais
- Re: Memory leak from ExecutorState co... Tomas Vondra
- Re: Memory leak from ExecutorState contex... Tomas Vondra
- Re: Memory leak from ExecutorState co... Jehan-Guillaume de Rorthais
- Re: Memory leak from ExecutorStat... Jehan-Guillaume de Rorthais
- Re: Memory leak from Executor... Tomas Vondra
- Re: Memory leak from Exe... Jehan-Guillaume de Rorthais
- Re: Memory leak from ExecutorStat... Tomas Vondra
- Re: Memory leak from Executor... Jehan-Guillaume de Rorthais
- Re: Memory leak from Exe... Tomas Vondra