Antonin Houska <[email protected]> wrote: > It was discussed earlier [1] and the concerns about possibly excessive > resource consumptions were addressed by [2]. So I think it the fix was just > forgotten. Attached here.
Sorry, I attached wrong patch. This is what I meant. -- Antonin Houska Web: https://www.cybertec-postgresql.com
>From b4d63a8a4e3f0061b48abd6526769a4db56edac8 Mon Sep 17 00:00:00 2001 From: Antonin Houska <[email protected]> Date: Mon, 20 Apr 2026 09:20:36 +0200 Subject: [PATCH] Do not check the REPLICATION attribute when running REPACK. Although REPACK (CONCURRENTLY) uses replication slots, there is no concern that the slot will leak data of other users because the MAINTAIN privilege on the table is required anyway. The REPLICATION attribute is also not needed to prevent REPACK from stealing slots from logical replication, since commit e76d8c749c introduces a limit on the maximum number of slots used by REPACK. --- src/backend/commands/repack_worker.c | 1 - 1 file changed, 1 deletion(-) diff --git a/src/backend/commands/repack_worker.c b/src/backend/commands/repack_worker.c index b17edd771e2..e4a4860805b 100644 --- a/src/backend/commands/repack_worker.c +++ b/src/backend/commands/repack_worker.c @@ -214,7 +214,6 @@ repack_setup_logical_decoding(Oid relid) /* * Make sure we can use logical decoding. */ - CheckSlotPermissions(); CheckLogicalDecodingRequirements(true); /* -- 2.47.3
