From: RonJohn2 (@RonJohn2) <noreply+RonJohn2@github.com>
To: reorg/pg_repack <noreply+reorg-pg_repack@github.com>
Subject: Re: [reorg/pg_repack] issue #485: Consider an option to build indexes before copying data during table repack
Date: Fri, 21 Aug 2026 02:59:41 +0000
Message-ID: <gh-reorg-pg_repack-485-c5364654428@github.com> (raw)
In-Reply-To: <gh-reorg-pg_repack-485@github.com>
References: <gh-reorg-pg_repack-485@github.com>
@sawanoboly how would you create **a new** index on this table? (Wouldn't that cause the same `"base/pgsql_tmp/...": No space left on device` issues?
Another option is to partition the table (maybe on the PK). That would certainly reduce the amount of data written to base/pgsql_tmp (and possibly eliminate the need to repack the older partitions).