[ovs-dev] [PATCH 2/2] ovsdb: timestamp database records to millisecond resolution.

[Ben Pfaff]

On Mon, Sep 09, 2013 at 06:05:43PM -0700, Paul Ingram wrote:
> The ovsdb-server compaction timing logic is written assuming milliscond
> resolution timestamps but ovsdb-server wrote second resolution timestamps.
> 
> This commit changes ovsdb-server to write millisecond resolution timestamps
> and ovsdb-tool to report millisecond timestamps.
> 
> This raises two compatibility issues:
> 1. When a new ovsdb-server or ovsdb-tool reads an old database, it will
> multiply by 1000 any timestamp it reads which is less than 1<<31. Since
> this date corresponds to Jan 16 1970 this is unlikely to cause a problem.
> 2. When an old ovsdb-tool reads a new database, it will interpret the
> millisecond timestamps as seconds and report dates in the far future; the
> time of this commit is reported as the year 45645 (each second since the
> epoch is interpreted as 16 minutes). (When an old ovsdb-server reads a
> new database there is no problem, it is already interpreting the timestamps
> in milliseconds).

Very clever, thanks, I'll apply this after we settle on the first one.

This patch also needs your sign-off.