...
> BTW, 7.2 assumes plain "timestamp" to denote "timestamp with time zone";
> this is for backwards compatibility with the behavior of previous
> releases' timestamp datatype. However, the SQL spec says that
> "timestamp" should mean ""timestamp without time zone", so we are
> probably going to change over eventually.
> (Hey Thomas, did I get all that right?)
Yes, including the change in default in an upcoming release. Well,
actually I have to admit I lost concentration somewhere in the middle of
the "power examples" so didn't check those carefully ;) :))
- Thomas