regarding bloat and fragmentation, if it's ensured that the long-running tx can access to only the table A, we can safely vacuum table B even while that tx is running? #pgconfasia
It's not that much additional information. We already have xmin, if we additionally track xmax it'd be sufficient. Why isn't that sufficient / why do we need variable amounts of storage?
-
-
And sure, testing each tuple gets more expensive, but it'd be quite reasonable to add heuristics about how old a tuple has to be to use the more expensive methodology - in which case it'd be much more likely to be worth the resources.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.