"Rison, Stuart" <[EMAIL PROTECTED]> 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 ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly