Re: why there is not VACUUM FULL CONCURRENTLY?

From: Antonin Houska <ah(at)cybertec(dot)at>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: why there is not VACUUM FULL CONCURRENTLY?
Date: 2024-07-09 15:55:58
Message-ID: 82651.1720540558@antos
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:

> > Is your plan to work on it soon or should I try to write a draft patch? (I
> > assume this is for PG >= 18.)
>
> I don't have plans for it, so if you have resources, please go for it.

The first version is attached. The actual feature is in 0003. 0004 is probably
not necessary now, but I haven't realized until I coded it.

--
Antonin Houska
Web: https://www.cybertec-postgresql.com

Attachment Content-Type Size
v01-0001-Adjust-signature-of-cluster_rel-and-its-subroutines.patch text/x-diff 14.9 KB
v01-0002-Move-progress-related-fields-from-PgBackendStatus-to.patch text/x-diff 6.4 KB
unknown_filename text/plain 195.4 KB
v01-0004-Call-logical_rewrite_heap_tuple-when-applying-concur.patch text/x-diff 24.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-07-09 15:59:05 Re: array_in sub function ReadArrayDimensions error message
Previous Message David G. Johnston 2024-07-09 15:40:08 Re: array_in sub function ReadArrayDimensions error message