Re: REPACK and naming - Mailing list pgsql-hackers

From David Rowley
Subject Re: REPACK and naming
Date
Msg-id CAApHDvrr1ZqdNnZ8exqz6vX9bGbr=WmCKj6kbKE1B+ay6FYh8Q@mail.gmail.com
Whole thread Raw
In response to Re: REPACK and naming  (Robert Haas <robertmhaas@gmail.com>)
Responses REPACK and naming
List pgsql-hackers
On Thu, 18 Sept 2025 at 01:09, Robert Haas <robertmhaas@gmail.com> wrote:
> RETABLE just isn't a word. The code sometimes calls this a REWRITE of
> a table, which would be reasonable.

+1. I was reading this yesterday wondering why "REWRITE" didn't get a
mention.  The problem I have with REPACK is that "re" indicates that
something is being re-done that's been done before. If you're calling
REPACK for the first time on a table, that's not true.

David J's "REBUILD" also seems ok.  In a green field, you could then
have "REBUILD TABLE ..." and "REBUILD INDEX ..."

David



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Remove PointerIsValid()
Next
From: Tom Lane
Date:
Subject: Re: New string-truncation warnings from GCC 15