Tags: reorg/pg_repack
Tags
pg_repack 1.5.3 released * Cleanup temporary indexes on error when using --only-indexes to avoid artefacts after failures (issue #437, pull request #440) * Acquire SHARE UPDATE EXCLUSIVE lock on the target table during a full-table repack instead of ACCESS SHARE (issue #420, pull request #452) * Fix subtransactions cache overflow (issue #457, pull request #460)
pg_repack 1.5.1 released * Added support for PostgreSQL 17 * Fix wrong OID format type in repack_trigger (issue #380) * Fix check of NOT NULL by repack.primary_keys (issue #282) * Fixed processing of tablespace names requiring quoted identifiers (issue #386) * Replace ``PQconnectdb()`` by ``PQconnectdbParams()`` (issue #382) * Added ``--apply-count`` option (issue #392) * Do not include a declaratively partitioned table with option ``--only-indexes`` (issue #389) * Fix possible two vacuums concurrently processing the same relfilenode (issue #399) * Use savepoints when retrying to take AccessShareLock (issue #383) * Fix swap of relfrozenxid, relfrozenxid and relallvisible (issue #377, #157)
pg_repack 1.5.0 released * Added support for PostgreSQL 16 * Fix possible SQL injection (issue #368) * Support longer password length (issue #357) * Fixed infinite loop on empty password (issue #354) * Added ``--switch-threshold`` option (issue #347) * Fixed crash in ``get_order_by()`` using invalid relations (issue #321) * Added support for tables that have been previously rewritten with `VACUUM FULL` and use storage=plain for all columns (issue #313) * More careful locks acquisition (issue #298)
* Fixed possible CVE-2018-1058 attack paths (issue #168) * Fixed "unexpected index definition" after CVE-2018-1058 changes in PostgreSQL (issue #169) * Fixed build with recent Ubuntu packages (issue #179)
PreviousNext