@ -2245,24 +2245,27 @@ TIMESTAMP '2004-10-19 10:23:54+02'
<programlisting>
<programlisting>
TIMESTAMP WITH TIME ZONE '2004-10-19 10:23:54+02'
TIMESTAMP WITH TIME ZONE '2004-10-19 10:23:54+02'
</programlisting>
</programlisting>
</para>
In a literal that has been determined to be <type>timestamp without time
<para>
In a value that has been determined to be <type>timestamp without time
zone</type>, <productname>PostgreSQL</productname> will silently ignore
zone</type>, <productname>PostgreSQL</productname> will silently ignore
any time zone indication.
any time zone indication.
That is, the resulting value is derived from the date/time
That is, the resulting value is derived from the date/time
fields in the input value , and is not adjusted for time zone.
fields in the input string , and is not adjusted for time zone.
</para>
</para>
<para>
<para>
For <type>timestamp with time zone</type>, the internally stored
For <type>timestamp with time zone</type> values, an input string
value is always in UTC (Universal
that includes an explicit time zone will be converted to UTC
Coordinated Time, traditionally known as Greenwich Mean Time,
(<glossterm linkend="glossary-utc">Universal Coordinated
<acronym>GMT</acronym>). An input value that has an explicit
Time</glossterm>) using the appropriate offset
time zone specified is converted to UTC using the appropriate offset
for that time zone. If no time zone is stated in the input string,
for that time zone. If no time zone is stated in the input string,
then it is assumed to be in the time zone indicated by the system's
then it is assumed to be in the time zone indicated by the system's
<xref linkend="guc-timezone"/> parameter, and is converted to UTC using the
<xref linkend="guc-timezone"/> parameter, and is converted to UTC using the
offset for the <varname>timezone</varname> zone.
offset for the <varname>timezone</varname> zone.
In either case, the value is stored internally as UTC, and the
originally stated or assumed time zone is not retained.
</para>
</para>
<para>
<para>