public inbox for [email protected]  
help / color / mirror / Atom feed
From: Jim Jones <[email protected]>
To: Álvaro Herrera <[email protected]>
Cc: Antonin Houska <[email protected]>
Cc: Chao Li <[email protected]>
Cc: Zsolt Parragi <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: VACUUM FULL, CLUSTER, and REPACK block on other sessions' temp tables
Date: Wed, 6 May 2026 08:33:29 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

On 05/05/2026 16:32, Álvaro Herrera wrote:
> I decided against pushing the other patch.  Although I would have
> preferred to add a test, its cost seems not trivial: there are three
> full-database scans in it (one for each command), and that seemed a bit
> excessive.  (There's also one extra initdb, but I'm not sure that part
> is too bad since we've optimized that particular part.)

Fair enough.

> I also considered backpatching, since the code has been like this
> essentially forever (i.e. at least since pg14).  However, I don't
> remember any complaints about this and I would hate to destabilize
> things for people without an excellent reason.  Maybe we can reconsider
> after this month's minors, if somebody shows up with vehement opinions
> about it.

Yeah, since pretty much nobody complained about it, I guess it's indeed 
safer to leave it in PG19.

Thanks for pushing it!

Best, Jim







view thread (2+ 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], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: VACUUM FULL, CLUSTER, and REPACK block on other sessions' temp tables
  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