From: | "Jose Tomas Eterovic" <roleroz(at)gmail(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #3761: Problems with to_char(timestamp) and milliseconds |
Date: | 2007-11-19 19:30:28 |
Message-ID: | 200711191930.lAJJUSnH045101@wwwmaster.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-patches |
The following bug has been logged online:
Bug reference: 3761
Logged by: Jose Tomas Eterovic
Email address: roleroz(at)gmail(dot)com
PostgreSQL version: 8.2.4-r1
Operating system: Gentoo Linux
Description: Problems with to_char(timestamp) and milliseconds
Details:
When you use to_char to show as a string a date (including milliseconds),
there's the possibility that the number of milliseconds will be 1000 (not
between 000-999 as the documentation says)
if you have a table (called "testTable") with a single column of type
"timestamp" (called "testTimestamp") with lots of data, and you run the
query
SELECT to_char(testTimestamp, 'YYYY-MM-DD HH24:MI:SS.MS') FROM testTable
you'll eventually get a result like
2007-10-24 13:44:48.1000
instead of
2007-10-24 13:44:49.000
From | Date | Subject | |
---|---|---|---|
Next Message | Hussain Jawad-FXRM43 | 2007-11-19 19:34:09 | Re: Start up error |
Previous Message | Bruce Momjian | 2007-11-19 19:27:15 | Re: BUG #3760: Comment on restore database |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-11-19 21:29:47 | Re: [BUGS] BUG #3761: Problems with to_char(timestamp) and milliseconds |
Previous Message | Tom Lane | 2007-11-19 18:37:48 | Re: [HACKERS] fulltext parser strange behave |