Re: ODBC Layer and the now() function

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Byrne Kevin-kbyrne01 <kbyrne01(at)motorola(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: ODBC Layer and the now() function
Date: 2005-12-05 14:59:22
Message-ID: 29463.1133794762@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Byrne Kevin-kbyrne01 <kbyrne01(at)motorola(dot)com> writes:
> Moserver receives the event - timestamps it as 't1'
> -- time lapse before moserver computes the transaction and gives it to odbc.
> Txn_begin- now() gets frozen to 't2'
> Insert - now() should put it as 't2'
> Txn_end()- done.

> So firstly t2 should always be > t1 and the difference could be a few seconds but I found sometimes t2 < t1!..

I'd wonder about clock skew between the machine that's running
"moserver" and the machine running Postgres.

Another possibility is that the "transaction begin" doesn't happen when
you think it does. Sometimes driver-level code like ODBC will issue
BEGIN behind your back ...

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Frank.Motzkat 2005-12-05 15:46:39 how to use SAVEPOINT in stored function
Previous Message Timothy Perrigo 2005-12-05 14:42:47 unsubscribe