Message-ID: <679b3979.5d0a0220.115578.3e08@mx.google.com>
Sender: Michael Banck <mbanck@gmail.com>
Date: Thu, 30 Jan 2025 09:34:01 +0100
From: Michael Banck <mbanck@gmx.net>
To: Antonin Houska <ah@cybertec.at>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
	Junwang Zhao <zhjwpku@gmail.com>,
	Kirill Reshke <reshkekirill@gmail.com>,
	Pavel Stehule <pavel.stehule@gmail.com>,
	Michael Paquier <michael@paquier.xyz>,
	PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: why there is not VACUUM FULL CONCURRENTLY?
References: <202501091952.df7vrzrundlo@alvherre.pgsql>
 <6250.1736776111@antos>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6250.1736776111@antos>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://www.postgresql.org/message-id/679b3979.5d0a0220.115578.3e08%40mx.google.com>
Precedence: bulk

Hi,

On Mon, Jan 13, 2025 at 02:48:31PM +0100, Antonin Houska wrote:
> Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> > On 2025-Jan-09, Antonin Houska wrote:
> > > It seems you accidentally fixed another problem :-) I was referring to the
> > > 'lockmode' argument of make_new_heap(). I can try to write a patch for that
> > > but ...
> > > 
> > > > Meanwhile the patch 0004 has some seemingly trivial conflicts.  If you
> > > > want to rebase, I'd appreciate that.  In the meantime I'll give a look
> > > > at the next two other API changes.
> 
> This is the patch series rebased on top of the commit cc811f92ba.
> 
> I haven't addressed the problem of a new command yet - for that I'd like to
> see some sort of consensus, so that I do not have to do all the related
> changes many times.

Well, looks like this patch-set is blocked on the bikeshedding part?

Somebody should call a shot here, then.


Michael