| From: | Edmund Dengler <edmundd(at)eSentire(dot)com> |
|---|---|
| To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Performance of a query |
| Date: | 2003-06-12 00:51:39 |
| Message-ID: | Pine.BSO.4.44.0306112050160.149-100000@cyclops4.esentire.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Doesn't seem to exist.
select current_user; ==> works.
select local_timestamp; ==> "ERROR: Attribute "local_timestamp" not
found".
Is this perhaps a deprecated constant? (Currently running 7.3.3)
Regards,
Ed
On Wed, 11 Jun 2003, Bruno Wolff III wrote:
> On Wed, Jun 11, 2003 at 20:11:02 -0400,
> Edmund Dengler <edmundd(at)eSentire(dot)com> wrote:
> > Greetings all!
> >
> > So I have had a look at the documentation to see what options I have in
> > separating the "select now() - '2 hours'::interval" from the rest of my
> > query. As far as I can tell, I have the following options:
>
> How about using local_timestamp instead of now? It returns a timestamp
> instead of a timestamptz and I suspect will do what you want.
> Whatever you are comparing it to will also need to be of type
> timestamp. I suspect that you should be careful when setting timezone in your
> transaction when doing things this way.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2003-06-12 01:11:02 | Re: Performance of a query |
| Previous Message | Bruno Wolff III | 2003-06-12 00:44:35 | Re: Performance of a query |