Re: I was spoiled by the MySQL timestamp field

At 05:00 PM 1/26/03 -0500, Tom Lane wrote:
>(BTW, the reason 'now' without "timestamp" in front works is that this
>is not a timestamp literal but a text literal, which will be coerced
>to timestamp at runtime.)

Is it known at the moment which of those methods the Postgresql team are 
aiming to continue supporting for the near/medium future?

e.g. current_timestamp is guaranteed. now() for the forseeable future. 
'now' for the next few versions.

Thanks,
Link.