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

From Bruno Wolff III
Subject Re: now() more precise than the transaction
Date
Msg-id 20030204195801.GB6016@wolff.to
Whole thread Raw
In response to Re: now() more precise than the transaction  (RobertD.Stewart@mail.state.ky.us)
Responses Re: now() more precise than the transaction
List pgsql-general
On Tue, Feb 04, 2003 at 14:27:03 -0500,
  RobertD.Stewart@mail.state.ky.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@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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly

pgsql-general by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: Drop constraint in PostgreSQL 7.1.2
Next
From: Andrew Sullivan
Date:
Subject: Re: Q: explain on delete