Re: REPACK and naming

From: Junwang Zhao <zhjwpku(at)gmail(dot)com>
To: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Subject: Re: REPACK and naming
Date: 2025-09-17 13:18:23
Message-ID: CAEG8a3LRvNtpqUGKYwxx+=vHW7rsDW+eqSVMP4auci=80os45w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 17, 2025 at 9:01 PM Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> wrote:
>
>
>
> Em ter., 16 de set. de 2025 às 13:40, Bruce Momjian <bruce(at)momjian(dot)us> escreveu:
>>
>> I am starting to get worried about the confusing of adding a REPACK
>> command. We already have a lot of confusion around vacuum and analyze:
>>
>> * autoanalyze does vacuum and analyze
>> * VACUUM FULL is much different from VACUUM
>>
>> It seems if we add REPACK as a command, it is somewhere between VACUUM
>> FULL and VACUUM in severity/impact. Should we be rethinking the naming
>> in this area?
>
> SqlServer has similar feature.
> SHRINK

C++ vector has a shrink_to_fit method which seems to serve a similar purpose.

REPACK or REBUILD looks good to me, COMPACT, on the other hand, feels
more specific to the idea of consolidating free space within a page or block.

>
> best regards,
> Ranier Vilela

--
Regards
Junwang Zhao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-09-17 13:31:03 Re: pgbench: remove an unused function argument
Previous Message Greg Burd 2025-09-17 13:17:59 Re: [PATCH] Add tests for Bitmapset