pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: doc: Update REPACK-related table rewrite documentation 2+ messages / 1 participants [nested] [flat]
* pgsql: doc: Update REPACK-related table rewrite documentation @ 2026-08-26 01:38 Fujii Masao <fujii@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: Fujii Masao @ 2026-08-26 01:38 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org doc: Update REPACK-related table rewrite documentation Adding REPACK introduced table-rewrite behavior that overlaps with VACUUM FULL and CLUSTER, but some documentation still mentioned only one of these commands or described the progress and locking behavior imprecisely. Clarify that table-rewriting operations, including REPACK, can change CTIDs. Also describe VACUUM FULL, CLUSTER, and REPACK consistently as table-rewriting operations for disk-space recovery where appropriate, document the pg_stat_progress_repack and compatibility pg_stat_progress_cluster views consistently, and clarify the ACCESS EXCLUSIVE locking behavior of REPACK, including CONCURRENTLY. Backpatch to v19, where REPACK was introduced. Author: Marcos Pegoraro <marcos@f10.com.br> Author: Fujii Masao <masao.fujii@gmail.com> Discussion: https://postgr.es/m/CAB-JLwaLcHyf=OnLnBsJEbdd57WjWPpK5T7iGFJvAQphjTZj_A@mail.gmail.com Backpatch-through: 19 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/872b20aa5649f9b90781961cbc404409783dab2b Modified Files -------------- doc/src/sgml/ddl.sgml | 4 +++- doc/src/sgml/maintenance.sgml | 45 ++++++++++++++++++++++++++----------------- doc/src/sgml/monitoring.sgml | 24 +++++++++++++---------- doc/src/sgml/mvcc.sgml | 12 ++++++++---- 4 files changed, 52 insertions(+), 33 deletions(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: doc: Update REPACK-related table rewrite documentation @ 2026-08-26 01:38 Fujii Masao <fujii@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: Fujii Masao @ 2026-08-26 01:38 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org doc: Update REPACK-related table rewrite documentation Adding REPACK introduced table-rewrite behavior that overlaps with VACUUM FULL and CLUSTER, but some documentation still mentioned only one of these commands or described the progress and locking behavior imprecisely. Clarify that table-rewriting operations, including REPACK, can change CTIDs. Also describe VACUUM FULL, CLUSTER, and REPACK consistently as table-rewriting operations for disk-space recovery where appropriate, document the pg_stat_progress_repack and compatibility pg_stat_progress_cluster views consistently, and clarify the ACCESS EXCLUSIVE locking behavior of REPACK, including CONCURRENTLY. Backpatch to v19, where REPACK was introduced. Author: Marcos Pegoraro <marcos@f10.com.br> Author: Fujii Masao <masao.fujii@gmail.com> Discussion: https://postgr.es/m/CAB-JLwaLcHyf=OnLnBsJEbdd57WjWPpK5T7iGFJvAQphjTZj_A@mail.gmail.com Backpatch-through: 19 Branch ------ REL_19_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/dc8628e55d443120f4759a969ec329474a838ee3 Modified Files -------------- doc/src/sgml/ddl.sgml | 4 +++- doc/src/sgml/maintenance.sgml | 45 ++++++++++++++++++++++++++----------------- doc/src/sgml/monitoring.sgml | 24 +++++++++++++---------- doc/src/sgml/mvcc.sgml | 12 ++++++++---- 4 files changed, 52 insertions(+), 33 deletions(-) ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2026-08-26 01:38 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2026-08-26 01:38 pgsql: doc: Update REPACK-related table rewrite documentation Fujii Masao <fujii@postgresql.org> 2026-08-26 01:38 pgsql: doc: Update REPACK-related table rewrite documentation Fujii Masao <fujii@postgresql.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox