Re: REPACK and naming

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: 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 02:01:03
Message-ID: CA+TgmoZd+AQzFa+6NfZoiECu2zdbkpowLzP_46ZORp+2E0jq2g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 16, 2025 at 7:42 PM Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> Peter E suggested that since we have REINDEX to rewrite indexes, then
> the command to rewrite tables should be RETABLE. I haven't been able to
> get myself to like that idea, and also I think that was a bit
> tongue-in-cheek, but if you like RETABLE better than REPACK, then maybe
> we can have a vote to decide which one of those names to use. However,
> I don't think that change would make a tremendous difference, and also I
> don't think RETABLE is enough of an English name to become a command
> name.

I think RETABLE is not a proposal to be taken seriously. That's
extremely confusing.

I don't love the name REPACK, but I think it's good enough. If we come
up with something better, great.

I agree that having a single command that does both VACUUM FULL and
CLUSTER makes a lot more sense than the status quo, which is a
confusing historical accident.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2025-09-17 02:08:28 Re: GB18030-2022 Support in PostgreSQL
Previous Message Michael Paquier 2025-09-17 01:16:58 Re: question about pending updates in pgstat_report_inj