Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f1LLuUx34308 for ; Wed, 21 Feb 2001 16:56:31 -0500 (EST) (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.1/8.11.1) with ESMTP id f1LLtX912326; Wed, 21 Feb 2001 16:55:33 -0500 (EST) To: Daniel Wickstrom cc: pgsql-sql@postgresql.org Subject: Re: now() with microsecond granulity needed In-reply-to: <14996.11186.111947.408165@gargle.gargle.HOWL> References: <20010220173146.E1718@blue.alter.pl> <12975.982688262@sss.pgh.pa.us> <20010221215416.C1718@blue.alter.pl> <14996.11186.111947.408165@gargle.gargle.HOWL> Comments: In-reply-to Daniel Wickstrom message dated "Wed, 21 Feb 2001 15:57:22 -0500" Date: Wed, 21 Feb 2001 16:55:33 -0500 Message-ID: <12323.982792533@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200102/330 X-Sequence-Number: 1526 Daniel Wickstrom writes: > the timeofday function seems to work: Hmm, exactly what I was thinking of, except that it returns a text rather than a timestamp (a strange choice...). It seems a little buggy as well because the formatting of the microseconds part is wrong --- will fix that, and document it. regards, tom lane