aboutsummaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorPaul Ingram <pingram@nicira.com>2013-09-13 18:52:54 -0700
committerBen Pfaff <blp@nicira.com>2013-09-16 10:55:16 -0700
commit1ff1065c32df20a751c3d33cf2f67b798c5cf119 (patch)
tree1e6f4d2ffb616f5ad6264b8ce8ba84a38cc745ca /NEWS
parent2958f35b7e1b2d468f6a908121d80e07c15ba22b (diff)
ovsdb: write commit timestamps to millisecond resolution.
This is expected to make system debugging easier. This raises two compatibility issues: 1. When a new 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 45672 (each second since the epoch is interpreted as 16 minutes). Signed-off-by: Paul Ingram <pingram@nicira.com> Signed-off-by: Ben Pfaff <blp@nicira.com>
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS5
1 files changed, 3 insertions, 2 deletions
diff --git a/NEWS b/NEWS
index 4dd956809..c46c3cc83 100644
--- a/NEWS
+++ b/NEWS
@@ -1,7 +1,8 @@
Post-v2.0.0
---------------------
- - Log files now report times with millisecond resolution. (Previous
- versions only reported whole seconds.)
+ - Log file timestamps and ovsdb commit timestamps are now reported
+ with millisecond resolution. (Previous versions only reported
+ whole seconds.)
v2.0.0 - xx xxx xxxx