Re: now() more precise than the transaction - Mailing list pgsql-general

From RobertD.Stewart@mail.state.ky.us
Subject Re: now() more precise than the transaction
Date
Msg-id 098C0DC713F9D311B2FB00508B95327605971737@agency2.state.ky.us
Whole thread Raw
In response to now() more precise than the transaction  (Gregory Stark <gsstark@mit.edu>)
Responses Re: now() more precise than the transaction
List pgsql-general
Try CURRENT_TIMESTAMP
You should be able to get your time that way

-----Original Message-----
From: Gregory Stark [mailto:gsstark@mit.edu]
Sent: Tuesday, February 04, 2003 2:28 PM
To: Postgresql General Mailing List
Subject: [GENERAL] now() more precise than the transaction


I know this was discussed a while back, and I just reviewed the discussion.
It
looks like the proposal was to make now('immediate') get the exact current
time.

But is there a way to get that now? I can't find anything in the FAQs or in
the 7.3 docs that indicates any of the functions do anything other than
now('transaction').

--
greg


---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

pgsql-general by date:

Previous
From: Gregory Stark
Date:
Subject: now() more precise than the transaction
Next
From: Bruno Wolff III
Date:
Subject: Re: not exactly a bug report, but surprising behaviour