Re: BUG #14558: to_timestamp() format lies about supporting timezone

John McKown <john(dot)archie(dot)mckown(at)gmail(dot)com> writes:
> On Mon, Feb 20, 2017 at 8:11 AM, <coladict(at)gmail(dot)com> wrote:
>> postgres=# SELECT to_timestamp('2017-02-20 16:00:27.989808+02', 'YYYY-MM-DD
>> HH24:MI:SS.SSSSOF')::timestamp with time zone;
>> ERROR: "TZ"/"tz"/"OF" format patterns are not supported in to_date

> I'm not a maintainer. Or any kind of an official "expert". But I'm
> wondering if the above is really a bug. From reading the documentation on:
> https://www.postgresql.org/docs/current/static/functions-datetime.html, it
> seems to me to say that to_timestamp() only takes one parameter, which is a
> double precision number (not a string).

Nah, that's the other function named to_timestamp. This one's documented
on the previous page:
https://www.postgresql.org/docs/current/static/functions-formatting.html

> Or was this an enhancement request?

Possibly. I'm choosing to read it as a complaint that the limitation
is not mentioned in the documentation, which seems to be true. I'll
go fix that.

(Actually supporting TZ/tz might be a bit hard, because you'd have
to figure out how to get to_timestamp's parser to see cases like
"America/New_York" or "GMT-03" as single tokens. Possibly the
omission of OF is just a lack of round tuits.)

> But the following worked well for me:
> tsh009=# SELECT '2017-02-20 16:00:27.989808+02'::timestamp;

Yeah, it's remarkable how many people insist on using to_timestamp
when the regular timestamp input function would serve them as well
or better.

regards, tom lane