> 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.
If I understood correctly, this new type of snapshot would help if there are long running transactions which can see this tuples. But if there are not long running transactions, it will be the same. Am i right? And what about don’t fetch actual min and max values from indexes whose columns doesn’t involved in join? -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
