Horton
Menu

Re: Adding REPACK [concurrently]

Alvaro Herrera <alvherre@alvh.no-ip.org>

View thread
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Robert Treat <rob@xzilla.net>
Cc: "Shinoda, Noriyoshi (PSD Japan FSI)" <noriyoshi.shinoda@hpe.com>, Antonin Houska <ah@cybertec.at>, Mihail Nikalayeu <mihailnikalayeu@gmail.com>, Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-03-12T19:45:24Z
Lists: pgsql-hackers 
On 2026-Mar-12, Robert Treat wrote:

> ISTM the user facing docs refer to cluster as an "obsolete" variant /
> spelling, rather than something marked as deprecated. This feels like
> it is meant to imply that the old functionality is not planned for
> removal in some future release (ie. deprecated), but that you may find
> that certain bits of support for it are already removed/broken. If
> that was the intention, I guess it gives justification to remove it
> now; that said it does seem rather unfriendly to not give any kind of
> bridge release to get from one side to the other, so I think the ideal
> would be to keep it for v19 and remove it in v20.

Yeah, I think "obsolete" rather than "deprecated" is correct, because I
don't see us removing either CLUSTER or VACUUM FULL.  On the other hand,
if you use pg_stat_progress_cluster while running REPACK CONCURRENTLY,
then the resulting report might not fully make sense.

But I agree it makes sense to keep the view in place until ... some
later release.  (Maybe v20, but also maybe a little later wouldn't
hurt.)

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"On the other flipper, one wrong move and we're Fatal Exceptions"
(T.U.X.: Term Unit X  - http://www.thelinuxreview.com/TUX/)

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Allow old WAL recycling during REPACK CONCURRENTLY

  2. Advance restart_lsn more eagerly in LogicalConfirmReceivedLocation

  3. Remove unnecessary signal handler change

  4. Improve REPACK (CONCURRENTLY) error messages some more

  5. Revert "Allow logical replication snapshots to be database-specific"

  6. Move REPACK (CONCURRENTLY) test out of stock regression tests

  7. REPACK: do not require REPLICATION or LOGIN

  8. Add missing initialization

  9. Simplify declaration of memcpy target

  10. Reserve replication slots specifically for REPACK

  11. doc: Add an example of REPACK (CONCURRENTLY)

  12. Allow logical replication snapshots to be database-specific

  13. Avoid different-size pointer-to-integer cast

  14. Fix valgrind failure

  15. Add CONCURRENTLY option to REPACK

  16. Rename cluster.c to repack.c (and corresponding .h)

  17. Allow index_create to suppress index_build progress reporting

  18. Make index_concurrently_create_copy more general

  19. Document the 'command' column of pg_stat_progress_repack

  20. Introduce the REPACK command

  21. Toggle logical decoding dynamically based on logical slot presence.

  22. Split vacuumdb to create vacuuming.c/h

  23. Remove ReorderBufferTupleBuf structure.

  24. Revert changes to CONCURRENTLY that "sped up" Xmin advance

  25. VACUUM: ignore indexing operations with CONCURRENTLY