Re: [SQL] [GENERAL] CURRENT_TIMESTAMP

Manfred Koizar <mkoi-pg@aon.at> writes:
> And one last thought:  There are applications out there that are not
> written for one specific database backend.  Having to replace
> CURRENT_TIMESTAMP by PG-specific now('statement') is just one more
> pain in trying to be portable across different backends.

Based on this discussion, it seems any application that depends on a
specific behavior of CURRENT_TIMESTAMP is going to have portability
problems anyway.  Even if we did change CURRENT_TIMESTAMP to match
now('statement'), it would not act exactly like anyone else's.
        regards, tom lane