REPACK: warn about skipping foreign partitions

Started by Zsolt Parragiabout 13 hours ago1 messageshackers
Beta feature

Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.

appliessuccessCI history

You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:

docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t253603
psql -h localhost -U postgres

Built from patchset v1 (message #1), August 29, 2026 at 09:34 PM.

Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:

git clone --branch t253603_1 https://github.com/hackorum-dev/postgres.git

In a checkout you already have, add the fork once:

git remote add hackorum https://github.com/hackorum-dev/postgres.git

then, for this patchset and every later one:

git fetch hackorum t253603_1 && git checkout t253603_1

Patchset v1 (message #1) is on t253603_1

Jump to latest
#1Zsolt Parragi
zsolt.parragi@percona.com

Hello

Repack/cluster errors out when called directly on a foreign table. In
contrast to vacuum, repack/cluster doesn't warn when the table itself
is local but has foreign partitions.

The attached patch adds a similar warning to these commands, making
this skip clearly visible to users.

Attachments:

t253603_1
0001-Warn-when-REPACK-or-CLUSTER-skips-a-foreign-table-pa.patchapplication/octet-stream; name=0001-Warn-when-REPACK-or-CLUSTER-skips-a-foreign-table-pa.patchDownload+63-4