+ * TABLEAM_SUPPORTS_LOGICAL_DECODING: every change to the relation's rows can
+ * be logically decoded, which needs the AM's resource manager to have an
+ * rm_decode callback. REPACK (CONCURRENTLY) checks this, as it would
+ * otherwise lose the changes made while it runs.
Doesn't it also require filtering (change_useless_for_repack)?
Also, the helper can crash with partitioned tables or views:
CREATE TABLE p (i int PRIMARY KEY, j int) PARTITION BY RANGE (i);
SELECT test_tableam_supports_features('p'::regclass, 1);
server closed the connection unexpectedly
LOG: client backend (PID 965976) was terminated by signal 11:
Segmentation fault
LOG: all server processes terminated; reinitializing