| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | mars(at)cannoncreek(dot)com |
| Cc: | pgsql-sql(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: [SQL] epoch to show millseconds |
| Date: | 2001-07-17 16:04:00 |
| Message-ID: | 25214.995385840@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-sql |
Mars G Miro <mars(at)cannoncreek(dot)com> writes:
> how do I make it accurate up to milliseconds value?
You don't. current_timestamp depends on the time() system call,
which only returns a number accurate to one second.
There is a higher-precision current time function in 7.1, but I
forget the details ... see the docs. IIRC it existed but was
buggy in 7.0, so you'll need to update.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-07-17 16:08:22 | Re: VACUUM ANALYZE |
| Previous Message | Karel Zak | 2001-07-17 15:52:05 | Re: [HACKERS] Translators wanted |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kapil Tilwani | 2001-07-17 16:14:40 | Fw: Query Optimisation required |
| Previous Message | Tom Lane | 2001-07-17 16:00:53 | Re: Select distinct and order by. |