Re: why there is not VACUUM FULL CONCURRENTLY?

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