Hi Thom, In my understanding, this is an expected beahcior as you mentioned,
A fix is already proposed for v20. 0008 in Antonin's "REPACK enhancements" series, "Make REPACK (CONCURRENTLY) MVCC-safe", carries the visibility info over to the new table [1][2]. Jochen hit the same problem on -bugs with a repeatable read session[3]. [1] https://commitfest.postgresql.org/patch/6957/ [2] https://www.postgresql.org/message-id/224072.1789577949@localhost [3] https://www.postgresql.org/message-id/[email protected] Regards, Shihao
