Re: Index on timestamp field, and now()

Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Tom Lane wrote:
> >> Correct, it's the now() function that's not cachable --- but you can get
> >> around that with the "timestamp 'now'" kluge.
>
> > Isn't CURRENT_TIMESTAMP the preferred method for this?
>
> Doesn't make any difference as far as this point is concerned.
> CURRENT_TIMESTAMP isn't cachable either.

My point was that CURRENT_TIMESTAMP in the more standard way; 'now' is a
PostgreSQL-ism.  Both work fine.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026