8f61e44efd
"Waiting for %d transactions to finish. First PID: %s" message. Display it on every loop through the SQL_XID_ALIVE check (i.e. every second), instead of only when the number of transactions we're waiting on changes -- previously, it was too easy for that important message to get lost in other messages. And don't display the message at all when running under pg_regress, i.e. as part of `make installcheck`. We had been getting occasional errors from pg_regress when autovacuum was running and that message got logged.
pg_repack -- Reorganize tables in PostgreSQL databases with minimal locks ========================================================================= - Homepage: http://reorg.github.com/pg_repack - Download: http://pgxn.org/dist/pg_repack/ - Development: https://github.com/reorg/pg_repack - Bug Report: https://github.com/reorg/pg_repack/issues - Mailing List: http://pgfoundry.org/mailman/listinfo/reorg-general pg_repack_ is a PostgreSQL extension which lets you remove bloat from tables and indexes, and optionally restore the physical order of clustered indexes. Unlike CLUSTER_ and `VACUUM FULL`_ it works online, without holding an exclusive lock on the processed tables during processing. pg_repack is efficient to boot, with performance comparable to using CLUSTER directly. Please check the documentation (in the ``doc`` directory or online_) for installation and usage instructions. All users of pg_reorg 1.1.9 or earlier, and pg_repack 1.2.0-beta1 or earlier, are **urged to upgrade** to the latest pg_repack version to fix a serious data corruption issue_. .. _pg_repack: http://reorg.github.com/pg_repack .. _CLUSTER: http://www.postgresql.org/docs/current/static/sql-cluster.html .. _VACUUM FULL: VACUUM_ .. _VACUUM: http://www.postgresql.org/docs/current/static/sql-vacuum.html .. _online: pg_repack_ .. _issue: https://github.com/reorg/pg_repack/issues/23 What about pg_reorg? -------------------- pg_repack is a fork of the pg_reorg_ project, which has proven hugely successful. Unfortunately new feature development on pg_reorg_ has slowed or stopped since late 2011. pg_repack was initially released as a drop-in replacement for pg_reorg, addressing some of the shortcomings of the last pg_reorg version (such as support for PostgreSQL 9.2 and EXTENSION packaging) and known bugs. pg_repack 1.2 introduces further new features (parallel index builds, ability to rebuild only indexes) and bugfixes. In some cases its behaviour may be different from the 1.1.x release so it shouldn't be considered a drop-in replacement: you are advised to check the documentation__ before upgrading from previous versions. .. __: pg_repack_ .. _pg_reorg: http://reorg.projects.pgfoundry.org/