On Thu, May 14, 2026 at 02:02:15PM -0400, Tom Lane wrote:
> Bruce Momjian <[email protected]> writes:
> > Okay, here is the patch with "conversion".
>
> timetz does store a UTC offset, so it needs to be discussed separately.
> I don't think applying the same verbiage to time and timestamp will
> produce anything except more confusion.
I see what you mean --- updated patch attached.
If we want to be more explicit we could change "including time zone
conversion" to "including time zone conversion to/from UTC".
--
Bruce Momjian <[email protected]> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index d8d91678e86..339fec8ac08 100644
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -264,13 +264,13 @@
<row>
<entry><type>timestamp [ (<replaceable>p</replaceable>) ] [ without time zone ]</type></entry>
<entry></entry>
- <entry>date and time (no time zone)</entry>
+ <entry>date and time (no time zone conversion)</entry>
</row>
<row>
<entry><type>timestamp [ (<replaceable>p</replaceable>) ] with time zone</type></entry>
<entry><type>timestamptz</type></entry>
- <entry>date and time, including time zone</entry>
+ <entry>date and time, including time zone conversion</entry>
</row>
<row>
@@ -1768,7 +1768,7 @@ SELECT 'abc \153\154\155 \052\251\124'::bytea;
<row>
<entry><type>timestamp [ (<replaceable>p</replaceable>) ] [ without time zone ]</type></entry>
<entry>8 bytes</entry>
- <entry>both date and time (no time zone)</entry>
+ <entry>both date and time (no time zone conversion)</entry>
<entry>4713 BC</entry>
<entry>294276 AD</entry>
<entry>1 microsecond</entry>
@@ -1776,7 +1776,7 @@ SELECT 'abc \153\154\155 \052\251\124'::bytea;
<row>
<entry><type>timestamp [ (<replaceable>p</replaceable>) ] with time zone</type></entry>
<entry>8 bytes</entry>
- <entry>both date and time, with time zone</entry>
+ <entry>both date and time, with time zone conversion</entry>
<entry>4713 BC</entry>
<entry>294276 AD</entry>
<entry>1 microsecond</entry>
@@ -2263,8 +2263,9 @@ TIMESTAMP WITH TIME ZONE '2004-10-19 10:23:54+02'
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
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.
+ In either case, the value is stored internally as UTC. The
+ originally stated or assumed time zone is not retained and
+ <emphasis>cannot</emphasis> be retrieved later.
</para>
<para>
