"Tom Lane" <[EMAIL PROTECTED]> writes: >> Consider a data loading job which has millions of INSERT statements in a >> file. >> Currently if you put them all in a transaction it takes a single snapshot and >> runs them all with the same snapshot. > >> If you reset xmin whenever you have no live snapshots then that job would be >> doing that between every INSERT statement. > > These statements are 100% nonsense.
Uhm, yeah, I somehow didn't write was I was thinking. I didn't mean to say we would be taking a new snapshot for each INSERT but that we would be resetting xmin for each INSERT. Whereas currently we only set xmin once when we set the serializable snapshot. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
