RE: Global snapshots - Mailing list pgsql-hackers

From tsunakawa.takay@fujitsu.com
Subject RE: Global snapshots
Date
Msg-id TYAPR01MB299037242B6A5C0B6F9C84AEFE629@TYAPR01MB2990.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: Global snapshots  ("Andrey V. Lepikhov" <a.lepikhov@postgrespro.ru>)
Responses Re: Global snapshots  ("Andrey V. Lepikhov" <a.lepikhov@postgrespro.ru>)
Re: Global snapshots  ("Andrey V. Lepikhov" <a.lepikhov@postgrespro.ru>)
List pgsql-hackers
From: Andrey V. Lepikhov <a.lepikhov@postgrespro.ru>
> Current state of the patch set rebased on master, 5aed6a1fc2.
> 
> It is development version. Here some problems with visibility still detected in
> two tests:
> 1. CSN Snapshot module - TAP test on time skew.
> 2. Clock SI implementation - TAP test on emulation of bank transaction.

I'm sorry to be late to respond.  Thank you for the update.

As discussed at the HighGo meeting, what do you think we should do about this patch set, now that we agreed that
Clock-SIis covered by Microsoft's patent?  I'd appreciate it if you could share some idea to change part of the
algorithmand circumvent the patent.
 

Otherwise, why don't we discuss alternatives, such as the Commitment Ordering?

I have a hunch that YugabyteDB's method seems promising, which I wrote in the following wiki.  Of course, we should
makeefforts to see if it's patented before diving deeper into the design or implementation.
 

Scaleout Design - PostgreSQL wiki
https://wiki.postgresql.org/wiki/Scaleout_Design


Regards
Takayuki Tsunakawa



pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: shared-memory based stats collector
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: In-placre persistance change of a relation