Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f6HG4Za24638; Tue, 17 Jul 2001 12:04:35 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f6HG40X25217; Tue, 17 Jul 2001 12:04:00 -0400 (EDT) To: mars@cannoncreek.com cc: pgsql-sql@postgresql.org, pgsql-general@postgresql.org Subject: Re: [SQL] epoch to show millseconds In-reply-to: <01071208393000.07133@hellraiser.cannoncreek.com> References: <01071208393000.07133@hellraiser.cannoncreek.com> Comments: In-reply-to Mars G Miro message dated "Thu, 12 Jul 2001 08:39:30 +0800" Date: Tue, 17 Jul 2001 12:04:00 -0400 Message-ID: <25214.995385840@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200107/610 X-Sequence-Number: 12631 Mars G Miro 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