Re: tracking commit timestamps

On 11/07/2014 07:07 PM, Petr Jelinek wrote:


> The list of what is useful might be long, but we can't have everything 
> there as there are space constraints, and LSN is another 8 bytes and I 
> still want to have some bytes for storing the "origin" or whatever you 
> want to call it there, as that's the one I personally have biggest 
> use-case for.
> So this would be ~24bytes per txid already, hmm I wonder if we can 
> pull some tricks to lower that a bit.
>

The reason why Jim and myself are asking for the LSN and not just the 
timestamp is that I want to be able to order the transactions. Jim 
pointed out earlier in the thread that just ordering on timestamp allows 
for multiple transactions with the same timestamp.

Maybe we don't need the entire LSN to solve that.  If you already have 
the commit timestamp maybe you only need another byte or two of 
granularity to order transactions that are within the same microsecond.