From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Remove overspecification of precision of CURRENT_TIMESTAMP, |
Date: | 2005-06-24 14:28:07 |
Message-ID: | 20050624142807.9B9485288D@svr1.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Log Message:
-----------
Remove overspecification of precision of CURRENT_TIMESTAMP, LOCALTIMESTAMP,
CURRENT_TIME, and LOCALTIME: now they just produce "timestamptz" not
"timestamptz(6)", etc. This makes the behavior more consistent with our
choice to not assign a specific default precision to column datatypes.
It should also save a few cycles at runtime due to not having to invoke
the round-to-given-precision functions.
I also took the opportunity to translate CURRENT_TIMESTAMP into "now()"
instead of an invocation of the timestamptz input converter --- this should
save a few cycles too.
Modified Files:
--------------
pgsql/src/backend/parser:
gram.y (r2.496 -> r2.497)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/gram.y.diff?r1=2.496&r2=2.497)
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2005-06-24 15:12:00 | pgsql: unbreak unicode/utf8 test |
Previous Message | Tatsuo Ishii | 2005-06-24 13:56:40 | pgsql: Allow direct conversion between EUC_JP and SJIS to improve |