Re: advancing snapshot's xmin
От | Tom Lane |
---|---|
Тема | Re: advancing snapshot's xmin |
Дата | |
Msg-id | 22651.1206547132@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: advancing snapshot's xmin (Gregory Stark <stark@enterprisedb.com>) |
Ответы |
Re: advancing snapshot's xmin
Re: advancing snapshot's xmin |
Список | pgsql-hackers |
Gregory Stark <stark@enterprisedb.com> writes: > 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. Right, but setting xmin within GetSnapshotData is essentially free. What I'm envisioning is that we lose the notion of "this is a serializable snapshot" that that function currently has, and just give it the rule "if MyProc->xmin is currently zero, then set it". Then the only additional mechanism needed is for the snapshot manager to detect when all snapshots are gone and zero out MyProc->xmin --- that would happen sometime during command shutdown, and per current discussion it shouldn't need a lock. regards, tom lane
В списке pgsql-hackers по дате отправления: