Re: tracking commit timestamps - Mailing list pgsql-hackers

From Steve Singer
Subject Re: tracking commit timestamps
Date
Msg-id BLU436-SMTP244603CD8EA872FCA539042DC830@phx.gbl
Whole thread Raw
In response to Re: tracking commit timestamps  (Petr Jelinek <petr@2ndquadrant.com>)
Responses Re: tracking commit timestamps  (Anssi Kääriäinen <anssi.kaariainen@thl.fi>)
Re: tracking commit timestamps  (Petr Jelinek <petr@2ndquadrant.com>)
Re: tracking commit timestamps  (Simon Riggs <simon@2ndQuadrant.com>)
Re: tracking commit timestamps  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
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.




pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Order of views in stats docs
Next
From: Greg Stark
Date:
Subject: Re: BRIN indexes - TRAP: BadArgument