> Maybe we need another type of snapshot that would accept any > non-vacuumable tuple. I really don't want SnapshotAny semantics here, > but a tuple that was live more recently than the xmin horizon seems > like it's acceptable enough. HeapTupleSatisfiesVacuum already > implements the right behavior, but we don't have a Snapshot-style > interface for it.
I have tried to implement this new type of snapshot that accepts any non-vacuumable tuples. We have tried this patch in our load environment. And it has smoothed out and reduced magnitude of the cpu usage peaks. But this snapshot does not solve the problem completely. Patch is attached.
snapshot_non_vacuumable.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
