From: Tom Lane <tgl@sss.pgh.pa.us>
To: jindrich@vavruska.cz
cc: pgsql-docs@lists.postgresql.org
Subject: Re: Section 4.1.2.7 contains false information
In-reply-to: <155482249597.1372.1459692771442036097@wrigleys.postgresql.org>
References: <155482249597.1372.1459692771442036097@wrigleys.postgresql.org>
Comments: In-reply-to PG Doc comments form <noreply@postgresql.org>
	message dated "Tue, 09 Apr 2019 15:08:15 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <18317.1554825430.1@sss.pgh.pa.us>
Date: Tue, 09 Apr 2019 11:57:10 -0400
Message-ID: <18318.1554825430@sss.pgh.pa.us>
Precedence: bulk

PG Doc comments form <noreply@postgresql.org> writes:
> QUOTE:
> The CAST() syntax conforms to SQL. The type 'string' syntax is a
> generalization of the standard: SQL specifies this syntax only for a few
> data types, but PostgreSQL allows it for all types. The syntax with :: is
> historical PostgreSQL usage, as is the function-call syntax.
> UNQUOTE

> In fact, this is not 100% true. TIMESTAMP 'string' does not work this way.

Looks like it works to me:

regression=# select timestamp '2019-04-09 11:49';
      timestamp      
---------------------
 2019-04-09 11:49:00
(1 row)

If you feel that the documentation is unclear, you need to be clearer
about how it's unclear ;-)

(Reading between the lines of this complaint and your adjacent one,
I kind of suspect that you were trying to use "TIMESTAMP something"
where the something wasn't a literal string constant.  But surely
4.1.2.7 makes it plain that the discussed syntax is for constants.
You might need to read 4.2.9 "Type Casts" instead.)

			regards, tom lane