Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit bfd0cd5

Browse files
committed
Clearly document that timestamp alone means timestamp without timezone,
per SQL standard, and mention 7.3 behavior at the end.
1 parent 413d34b commit bfd0cd5

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

doc/src/sgml/datatype.sgml

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.244 2010/02/24 15:54:31 momjian Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.245 2010/02/25 18:16:53 momjian Exp $ -->
22

33
<chapter id="datatype">
44
<title id="datatype-title">Data Types</title>
@@ -1523,9 +1523,11 @@ SELECT E'\\xDEADBEEF';
15231523

15241524
<note>
15251525
<para>
1526-
Prior to <productname>PostgreSQL</productname> 7.3, writing just
1527-
<type>timestamp</type> was equivalent to <type>timestamp with
1528-
time zone</type>. This was changed for SQL compliance.
1526+
The SQL standard requires that writing just <type>timestamp</type>
1527+
be equivalent to <type>timestamp <emphasis>without</> time
1528+
zone</type>, and <productname>PostgreSQL</productname> honors that
1529+
behavior. (Releases prior to 7.3 treated it as <type>timestamp
1530+
with time zone</type>.)
15291531
</para>
15301532
</note>
15311533

0 commit comments

Comments
 (0)