Hi, On Thu, Aug 27, 2026 at 9:23 AM Nathan Bossart <[email protected]> wrote: > > 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?
Logical decoding doesn't check the table AM type, but goes ahead and decodes the WAL records (for that matter, none of CLUSTER, VACUUM FULL, and REPACK have checks on table AM. They hand off at some point to the table AM layer). I'm not sure if gating it just for concurrent repack is the right choice. Is it that we want to have it just for concurrent repack since it's new code with a new logical decoding plugin and we want some field reports of needing it for other table AMs? -- Bharath Rupireddy Amazon Web Services: https://aws.amazon.com
