pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Guo <guofenglinux@gmail.com>
Cc: jinhui.lai@qq.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19363: PostgreSQL shared memory exhaustion during query execution involving views and parallel workers
Date: Sat, 27 Dec 2025 16:33:19 -0500
Message-ID: <2380298.1766871199@sss.pgh.pa.us> (raw)
In-Reply-To: <1712093.1766854937@sss.pgh.pa.us>
References: <19363-8dd32fc7600a1153@postgresql.org>
	<CAMbWs4_Wp7D8k53OuQNhW9=iN2NQF+W0KPD+za0ehf6-F=Dcyg@mail.gmail.com>
	<1712093.1766854937@sss.pgh.pa.us>

I wrote:
> What I'm wondering is why this plan was accepted at all.  Does PHJ
> not consider work_mem or a similar limit on hash table size?

Ah, found it.  See

https://www.postgresql.org/message-id/2380165.1766871097%40sss.pgh.pa.us

			regards, tom lane





view thread (4+ messages)

Message-ID: <2380298.1766871199@sss.pgh.pa.us>
Permalink:  ../2380298.1766871199@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2380298.1766871199@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, guofenglinux@gmail.com, jinhui.lai@qq.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #19363: PostgreSQL shared memory exhaustion during query execution involving views and parallel workers
  In-Reply-To: <2380298.1766871199@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox