Samantha Atkins wrote: > OK, I read it again. I don't see anything about how the timezone is > specified for this type of column. What differs between timestamp and timestamptz is the behavior on input and output, but in both cases what is effectively stored is only an UTC timestamp, no timezone. That's unlike what the name of the type, "timestamp with time zone", seems to imply. One would expect that that would represent a certain value of timestamp along with a certain value of time zone, but that's not the case. Personally I think it's a rather unfortunate choice of name, but maybe that comes straight from the SQL standard. Oracle has a similar datatype and they call it "timestamp with local time zone", I guess it's a bit less confusing, as least it gives a hint that there is a local-related thing to be aware of. Anyway see http://www.postgresql.org/docs/8.2/interactive/datatype-datetime.html especially chapter 8.5.1.3 ! -- Daniel PostgreSQL-powered mail user agent and storage: http://www.manitou-mail.org ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
