Re: BUG #6391: insert does not insert correct value

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: john(dot)udick(at)zionsbancorp(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6391: insert does not insert correct value
Date: 2012-01-11 15:21:14
Message-ID: 19647.1326295274@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

john(dot)udick(at)zionsbancorp(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2012-01-11 15:24:50 Re: BUG #6393: cluster sometime fail under heavy concurrent write load
Previous Message Heikki Linnakangas 2012-01-11 15:17:12 Re: BUG #6392: leak memory while restore/load dump