Re: Doing INTERVAL with NOW() versus casted timestamp - Mailing list pgsql-general

From Andreas Kretschmer
Subject Re: Doing INTERVAL with NOW() versus casted timestamp
Date
Msg-id 20130216154158.GA2849@tux
Whole thread Raw
In response to Doing INTERVAL with NOW() versus casted timestamp  (Wells Oliver <wellsoliver@gmail.com>)
List pgsql-general
Wells Oliver <wellsoliver@gmail.com> wrote:

> Why does this give me two different results? 'created' is a date field:
>
> SELECT * FROM foo WHERE created >= '2013-02-16 00:00:00'::timestamp - INTERVAL
> '24 hours'

test=# select '2013-02-16 00:00:00'::timestamp - INTERVAL '24 hours';
      ?column?
---------------------
 2013-02-15 00:00:00
(1 row)




>
> and
>
> SELECT * FROM foo WHERE created >= NOW() - INTERVAL '24 hours'

test=*# select now() - INTERVAL '24 hours';
           ?column?
-------------------------------
 2013-02-15 16:38:51.362674+01
(1 row)



>
> First returns the 12 rows I expect where the 'created' field is 2012-02-15,
> second returns only one.


You can see the difference?






Andreas
--
Really, I'm not out to destroy Microsoft. That will just be a completely
unintentional side effect.                              (Linus Torvalds)
"If I was god, I would recompile penguin with --enable-fly."   (unknown)
Kaufbach, Saxony, Germany, Europe.              N 51.05082°, E 13.56889°

pgsql-general by date:

Previous
From: Wells Oliver
Date:
Subject: Doing INTERVAL with NOW() versus casted timestamp
Next
From: John Shott
Date:
Subject: Re: Doing INTERVAL with NOW() versus casted timestamp