From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | RobertD(dot)Stewart(at)mail(dot)state(dot)ky(dot)us |
Cc: | gsstark(at)mit(dot)edu, pgsql-general(at)postgresql(dot)org |
Subject: | Re: now() more precise than the transaction |
Date: | 2003-02-04 19:58:01 |
Message-ID: | 20030204195801.GB6016@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Feb 04, 2003 at 14:27:03 -0500,
RobertD(dot)Stewart(at)mail(dot)state(dot)ky(dot)us wrote:
> Try CURRENT_TIMESTAMP
> You should be able to get your time that way
I think he wants timeofday. CURRENT_TIMESTAMP should be the same as
now('transaction'), which I think he said wasn't what he wanted.
>
> -----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?
>
> http://archives.postgresql.org
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
From | Date | Subject | |
---|---|---|---|
Next Message | Vilson farias | 2003-02-04 20:20:47 | Re: Drop constraint in PostgreSQL 7.1.2 |
Previous Message | Stephan Szabo | 2003-02-04 19:56:21 | Re: not exactly a bug report, but surprising behaviour |