Re: BUG #6391: insert does not insert correct value - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #6391: insert does not insert correct value
Date
Msg-id 19647.1326295274@sss.pgh.pa.us
Whole thread Raw
In response to BUG #6391: insert does not insert correct value  (john.udick@zionsbancorp.com)
Responses Re: BUG #6391: insert does not insert correct value  (John Udick <John.Udick@zionsbancorp.com>)
List pgsql-bugs
john.udick@zionsbancorp.com writes:
> I would expect that at the time/date of the of now() and clock_timestamp()
> to be equal; which they are.

Well, they are not in general, but that doesn't appear to be your
problem.  You have not shown us a reproducible test case, but I wonder
whether your table has a trigger that is doing date_trunc('year',...)
or something like that on the column value.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: BUG #6392: leak memory while restore/load dump
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #6393: cluster sometime fail under heavy concurrent write load