Re: Index on timestamp field, and now()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Denis Perchine <dyp(at)perchine(dot)com>, lockhart(at)fourpalms(dot)org, pgsql-general(at)postgresql(dot)org
Subject: Re: Index on timestamp field, and now()
Date: 2002-02-12 18:08:14
Message-ID: 22586.1013537294@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2002-02-12 18:11:57 Re: Index on timestamp field, and now()
Previous Message Bruce Momjian 2002-02-12 17:59:31 Re: Index on timestamp field, and now()