database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-21 12:05:57 +03:00
Code

Update interval documenation to mention the storage system used.

Browse Source
This commit is contained in:
Bruce Momjian 2005-12-22 21:45:30 +00:00
parent 14e9a17f0a
commit f545a05704
1 changed files with 16 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
doc/src/sgml/datatype.sgml
View File

@ -1,5 +1,5 @@
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.163 2005/10/22 19:33:57 tgl Exp $ $PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.163.2.1 2005/12/22 21:45:30 momjian Exp $
--> -->
<chapter id="datatype"> <chapter id="datatype">
@ -1841,9 +1841,20 @@ January 8 04:05:06 1999 PST
</para> </para>
<para> <para>
The optional precision The optional subsecond precision <replaceable>p</replaceable> should
<replaceable>p</replaceable> should be between 0 and 6, and be between 0 and 6, and defaults to the precision of the input literal.
defaults to the precision of the input literal. </para>
<para>
Internally <type>interval</> values are stored as months, days,
and seconds. This is done because the number of days in a month
varies, and a day can have 23 or 25 hours if a daylight savings
time adjustment is involved. Because intervals are usually created
from constant strings or <type>timestamp</> subtraction, this
storage method works well in most cases. Functions
<function>justify_days</> and <function>justify_hours</> are
available for adjusting days and hours that overflow their normal
periods.
</para> </para>
</sect3> </sect3>
@ -1936,7 +1947,7 @@ January 8 04:05:06 1999 PST
<literal>CURRENT_DATE</literal>, <literal>CURRENT_TIME</literal>, <literal>CURRENT_DATE</literal>, <literal>CURRENT_TIME</literal>,
<literal>CURRENT_TIMESTAMP</literal>, <literal>LOCALTIME</literal>, <literal>CURRENT_TIMESTAMP</literal>, <literal>LOCALTIME</literal>,
<literal>LOCALTIMESTAMP</literal>. The latter four accept an <literal>LOCALTIMESTAMP</literal>. The latter four accept an
optional precision specification. (See <xref optional subsecond precision specification. (See <xref
linkend="functions-datetime-current">.) Note however that these are linkend="functions-datetime-current">.) Note however that these are
SQL functions and are <emphasis>not</> recognized as data input strings. SQL functions and are <emphasis>not</> recognized as data input strings.
</para> </para>