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
I think it'd be more promising to start vacuuming rows that are newer than the longrunning transaction, but already deleted. That'd not require the restriction of not accessing new tables in old transaction, which I don't see us exposing to SQL.
-
-
The trick there is the bookkeeping involved. You have to store snapshots (or something) in shared memory so you can identify what can be vacuumed, which requires a variable amount of storage, and makes testing each tuple a slower process.
-
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?
- 1 more reply
New conversation -
-
-
We could also track longest running transaction per database
-
I'm not seeing how that's related to the discussion?
- 2 more replies
New conversation -
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.