aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/jsonb_util.c
diff options
context:
space:
mode:
authorSimon Riggs <simon@2ndQuadrant.com>2014-12-08 23:32:03 +0900
committerSimon Riggs <simon@2ndQuadrant.com>2014-12-08 23:32:03 +0900
commit519b0757a37254452e013ea0ac95f4e56391608c (patch)
treed70193f9552c68c7b7e5c51a7e98a02fdff4e178 /src/backend/utils/adt/jsonb_util.c
parent611d46ea67c0863ab1d97c73c8cead1ed5ca82f0 (diff)
downloadpostgresql-519b0757a37254452e013ea0ac95f4e56391608c.tar.gz
postgresql-519b0757a37254452e013ea0ac95f4e56391608c.zip
Use GetSystemTimeAsFileTime directly in win32
PostgreSQL was calling GetSystemTime followed by SystemTimeToFileTime in the win32 port gettimeofday function. This is not necessary and limits the reported precision to the 1ms granularity that the SYSTEMTIME struct can represent. By using GetSystemTimeAsFileTime we avoid unnecessary conversions and capture timestamps at 100ns granularity, which is then rounded to 1µs granularity for storage in a PostgreSQL timestamp. On most Windows systems this change will actually have no significant effect on timestamp resolution as the system timer tick is typically between 1ms and 15ms depending on what timer resolution currently running applications have requested. You can check this with clockres.exe from sysinternals. Despite the platform limiation this change still permits capture of finer timestamps where the system is capable of producing them and it gets rid of an unnecessary syscall. The higher resolution GetSystemTimePreciseAsFileTime call available on Windows 8 and Windows Server 2012 has the same interface as GetSystemTimeAsFileTime, so switching to GetSystemTimeAsFileTime makes it easier to use the Precise variant later. Craig Ringer, reviewed by David Rowley
Diffstat (limited to 'src/backend/utils/adt/jsonb_util.c')
0 files changed, 0 insertions, 0 deletions