Re: Something wrong with binding timestamp values

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> OK, I found out that it used to bind such values as timestamptz, which failed
> when the receiving type was a timestamp (without time zone). But it should
> work the other way around, namely binding them as timestamp without time
> zone, because that can be casted implicitly to timestamptz.

Only for rather small values of "work" I'm afraid --- in particular,
that would cause any timezone specification in the input string to
be ignored, which is OK for timestamp without tz but surely not OK
for the other.

regards, tom lane