public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tomas Vondra <[email protected]>
To: Melanie Plageman <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Adjusting hash join memory limit to handle batch explosion
Date: Wed, 19 Feb 2025 21:21:59 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<CAAKRu_bYZvc3gHa+PnE2BTwbu1xX3MgyG+99-MZh7Rg5QyOEEA@mail.gmail.com>
	<[email protected]>
	<CAAKRu_aBW=NKGPK=+d_Xc0uk2ci47x7uej3WGUjgQSRLdnFyqw@mail.gmail.com>
	<[email protected]>
	<CAAKRu_YiLv24QKKJvUtDoO+=tw9Z5mt2i1g5=0992nmtwRekBQ@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CAAKRu_Zu59jWM+WCWUyc_W8x6VQ1HqX7FGDhV2cJj07E_Li9ug@mail.gmail.com>
	<[email protected]>
	<[email protected]>

I've pushed the first (and main) part of the patch series, after some
more cleanup and comment polishing.

As explained in my previous message, I'm not sure about 0002. I don't
know if we need to worry about it (no reports AFAICS). And while the
patch works I'm not sure it's the best fix, or whether we need to do
something about exhausting hash bits.

In any case, it's not PG18 material. And it's a separate issue, so I'm
marking this as committed.


Thanks everyone who helped with any of the many old patch versions!


-- 
Tomas Vondra

view thread (10+ messages)

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: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Adjusting hash join memory limit to handle batch explosion
  In-Reply-To: <[email protected]>

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

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