Re: REPACK and naming

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: REPACK and naming
Date: 2025-09-17 13:48:11
Message-ID: CAKFQuwbDajcN5vqL29WQ_iWpwHWTHLWxUYnqCxaJyU1ZhmQaHg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wednesday, September 17, 2025, Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
wrote:

> On 2025-Sep-17, David G. Johnston wrote:
>
> > Concretely, maybe we should remove vacuum full from the vacuum command
> > page, and just call it out as compatibility spelling of repack on its
> > page. Maybe do the same for cluster (I haven’t dived into the new
> feature
> > enough to confidently describe all this yet though).
>
> I think we should list VACUUM FULL as deprecated, document that feature
> in the REPACK documentation page, and leave VACUUM FULL in working state
> so as not to break existing scripts. Same for CLUSTER.
>

I was unclear - this is indeed what I suggesting as well. Reframe the
documentation but leave the commands functioning.

David J.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2025-09-17 13:55:12 Re: [PATCH] Add tests for Bitmapset
Previous Message Álvaro Herrera 2025-09-17 13:38:53 Re: REPACK and naming