REPACK (CONCURRENTLY) replays changes by decoding them from WAL, so it needs the table AM to be logically decodable, but check_concurrent_repack_requirements() doesn't check that. Should it be restricted to heap for v19?
-- nathan
REPACK (CONCURRENTLY) replays changes by decoding them from WAL, so it needs the table AM to be logically decodable, but check_concurrent_repack_requirements() doesn't check that. Should it be restricted to heap for v19?
-- nathan