Improve REPACK (CONCURRENTLY) error when wal_level < replica The error emitted when REPACK (CONCURRENTLY) is run with too low a wal_level is thrown by CheckSlotRequirements(), which is a bit mysterious when the user doesn't know what's up. Add an upfront check in check_concurrent_repack_requirements() for a more explicit, REPACK- centered report, which is easier to understand -- this also saves starting the worker just to have it die immediately.
Author: Baji Shaik <[email protected]> Reviewed-by: Chao Li <[email protected]> Discussion: https://postgr.es/m/CA+fm-ROdgh0rEVuXoViBk4TVgjodrN=mtr_ryuouklz9vox...@mail.gmail.com Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/43649b6a53e9b3964e921cc962f5c977bce688fd Modified Files -------------- src/backend/commands/repack.c | 9 +++++++++ 1 file changed, 9 insertions(+)
