Re: our friend the win32 system timer.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
Cc: pgsql-hackers-win32(at)postgresql(dot)org
Subject: Re: our friend the win32 system timer.
Date: 2004-08-16 23:05:05
Message-ID: 18353.1092697505@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers-win32

"Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> writes:
> This means that a table with a timestamp column defaulted to now() and a
> unique constraint on that column will have a very high chance of
> constraint violations. This might happen when reading in values from a
> script, and it works fine on Linux.

Any application that assumes it will get unique results from now() is
broken by definition. The fact that it manages not to fail on some
platforms doesn't make it less broken.

regards, tom lane

In response to

Responses

Browse pgsql-hackers-win32 by date

  From Date Subject
Next Message Bruce Momjian 2004-08-17 02:43:25 Re: libpq build problem with <io.h> on MS VC++
Previous Message Tom Lane 2004-08-16 22:32:07 Re: REPOST: InitDB Failure on install