Just had an idea and could use some feedback. If we start a transaction, leave it idle, and use pg_export_snapshot() to get its snapshot_id MVCC will hold all the tuples as of that transaction's start and any other transaction can see the state of the database as of that time using SET TRANSACTION SNAPSHOT snapshot_id?
I'm thinking of setting up automation to ~every half hour open a transaction as such, close any that have been open over an hour, and store the snapshot_id. However, I don't have a busy system that I can test it on.
Of course this would cause some extra bloat because those tuples cannot get autovacuumed until the transaction closes but that is also the case in Oracle. Is there anything else I am missing or a reason that this would not be possible?
