Alvaro Herrera <[email protected]> wrote: > So, if we're unable to get this particular patch in, we would have to > have a big fat warning in the docs, telling people to be careful about > other load if they choose to run concurrent repack -- it could have > serious consequences. But on the other hand, it's better to *have* the > tool, even if it has problems, than not have it. Keep in mind that > pg_repack and pg_squeeze also have all these problems/limitations (and > others), and still people use them.
1. To be precise, pg_squeeze has this limitation. pg_repack does not use logical replication. 2. I expect the limitation of PG core to be relaxed in versions > 19, as long as we integrate the MVCC safety feature. REPACK will then run w/o XID most of the time (XID will only be needed for catalog changes), so other decoding backends won't need to wait for its completion. -- Antonin Houska Web: https://www.cybertec-postgresql.com
