BUG #4853: millisecond is incorrect?

From: "Hiromichi Nakajima" <hirolin7(at)yahoo(dot)co(dot)jp>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #4853: millisecond is incorrect?
Date: 2009-06-15 09:40:00
Message-ID: 200906150940.n5F9e0FJ094758@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 4853
Logged by: Hiromichi Nakajima
Email address: hirolin7(at)yahoo(dot)co(dot)jp
PostgreSQL version: 8.3.7
Operating system: RedHatEnterpriseLinux ES3
Description: millisecond is incorrect?
Details:

for example
'OPE_DATE' field is timestamp with time zone.
I execute sql below:
INSERT INTO A_TBL ( OPE_DATE) VALUES ( '2009-06-15 18:29:58.156')
and show value with sql below:
select TO_CHAR ( OP_DATE, 'YYYY-MM-DD HH24:MI:SS.MS.US')
It must show as '2009-06-15 18:29:58.156.156000'
but sometimes '2009-06-15 18:29:58.156.155999'
Is it bug?
This doesn't occur on 8.2.4.
Thank you.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2009-06-15 14:28:55 Re: BUG #4853: millisecond is incorrect?
Previous Message Michael Schurat 2009-06-15 08:33:05 BUG #4852: PostgreSQL ODBC driver doesn't work