From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rison, Stuart <srison@rvc.ac.uk>
Cc: 'pgsql-sql@postgresql.org' <pgsql-sql@postgresql.org>
Cc: 'pgsql-bugs@postgresql.org' <pgsql-bugs@postgresql.org>
Subject: Re: [SQL] [SQL/BUGS] (possible) inconsistent behaviour of timestamp?
Date: Tue, 26 Nov 2002 21:14:54 -0500
Message-ID: <13005.1038363294@sss.pgh.pa.us> (raw)
In-Reply-To: <6BD8CE460CC6EE40B83DDFCED609F84BE140D8@cmnt4008.rvc.ac.uk>
References: <6BD8CE460CC6EE40B83DDFCED609F84BE140D8@cmnt4008.rvc.ac.uk>
"Rison, Stuart" <srison@rvc.ac.uk> writes:
> The first SELECT returns a 'timestamp', but the next two return a
> 'timestamptz' (presumably with timezone); is this inconsitent behaviour?
Yes. It's a transitional behavior in 7.2: timestamp without any quotes
is translated by the parser to timestamptz (ie, timestamp with time
zone). Quotes suppress the renaming, however.
We did that deliberately for one release to ease updating, because PG's
old "datetime" datatype corresponds to timestamptz, not timestamp-without-
time-zone. As of 7.3 that renaming doesn't happen any more, and
undecorated timestamp means timestamp without time zone, per spec.
Confused yet? I'm not sure that this update plan was really a great
idea, but we agreed to it a release or two back, and we're sticking to
it...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, srison@rvc.ac.uk, pgsql-bugs@postgresql.org
Subject: Re: [SQL] [SQL/BUGS] (possible) inconsistent behaviour of timestamp?
In-Reply-To: <13005.1038363294@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox