Re: [HACKERS] Proposal for CSN based snapshots

2013-06-07 Thread Ants Aasma
On Fri, Jun 7, 2013 at 2:59 PM, Markus Wanner mar...@bluegap.ch wrote: To refresh your memory the basic idea is to change visibility determination to be based on a commit sequence number (CSN for short) - a 8 byte number incremented on every commit representing the total ordering of commits.

Re: [HACKERS] Proposal for CSN based snapshots

2013-06-07 Thread Ants Aasma
On Fri, Jun 7, 2013 at 3:47 PM, Greg Stark st...@mit.edu wrote: On Thu, Jun 6, 2013 at 11:42 PM, Ants Aasma a...@cybertec.at wrote: To refresh your memory the basic idea is to change visibility determination to be based on a commit sequence number (CSN for short) - a 8 byte number incremented

Re: [HACKERS] Proposal for CSN based snapshots

2013-06-07 Thread Kevin Grittner
Ants Aasma a...@cybertec.at wrote: Serializable transactions - I won't pretend to be familiar with SSI code, but as far as I can tell serializable transactions don't need any modifications to work with the CSN based snapshot scheme. There actually already is a

[HACKERS] Proposal for CSN based snapshots

2013-06-06 Thread Ants Aasma
Given the recent ideas being thrown about changing how freezing and clog is handled and MVCC catalog access I thought I would write out the ideas that I have had about speeding up snapshots in case there is an interesting tie in with the current discussions. To refresh your memory the basic idea

<    1   2