| From: | RobertD(dot)Stewart(at)mail(dot)state(dot)ky(dot)us |
|---|---|
| To: | gsstark(at)mit(dot)edu, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: now() more precise than the transaction |
| Date: | 2003-02-04 19:27:03 |
| Message-ID: | 098C0DC713F9D311B2FB00508B95327605971737@agency2.state.ky.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Try CURRENT_TIMESTAMP
You should be able to get your time that way
-----Original Message-----
From: Gregory Stark [mailto:gsstark(at)mit(dot)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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2003-02-04 19:27:34 | now() more precise than the transaction |
| Previous Message | Gregory Stark | 2003-02-04 19:11:20 | not exactly a bug report, but surprising behaviour |