From: | Byrne Kevin-kbyrne01 <kbyrne01(at)motorola(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Anomalies with the now() function |
Date: | 2005-11-17 12:30:36 |
Message-ID: | 496E31A690F7D311B93C0008C789494C122463FC@zei02exm01.cork.cig.mot.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I have a trigger set up on a db - when a row is added to a certain table (say Table A) in my db the trigger calls a function and then the function enters another line in a related table (say Table B). Here's the problem, the first addition to Table A may show the time of the addition as, for example 19:01:53. This is correct. The second addition, triggered by the first additon, shows a time of say 19:01:10! The addition of the row to Table B uses the now() function to determine the time the new row is added to the table. This should in theory match the time (to within a few milliseconds at least) the first row was added, since the trigger is immediate. However, I am seeing major time differences? How reliable is now() - has anyone seen anything similar ?
Reagards,
Kevin Byrne
From | Date | Subject | |
---|---|---|---|
Next Message | john.bender | 2005-11-17 12:49:42 | Re: Rebranding PostgreSQL |
Previous Message | Markus Wollny | 2005-11-17 12:12:22 | Re: Incomplete Startup Packet |