database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-03 01:21:48 +03:00
Code

doc: interval spill method for units greater than months

Browse Source 
Units are _truncated_ to months, but only in back branches since the
recent commit.

Reported-by: Bryn Llewellyn

Discussion: https://postgr.es/m/BDAE4B56-3337-45A2-AC8A-30593849D6C0@yugabyte.com

Backpatch-through: 9.6 to 14
This commit is contained in:
Bruce Momjian 2021-08-03 12:17:58 -04:00
parent 49e319ceac
commit 606d041cb9
1 changed files with 14 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -2710,15 +2710,18 @@ P <optional> <replaceable>years</replaceable>-<replaceable>months</replaceable>-
</para> </para>
<para> <para>
In the verbose input format, and in some fields of the more compact Field values can have fractional parts: for example, <literal>'1.5
input formats, field values can have fractional parts; for example weeks'</literal> or <literal>'01:02:03.45'</literal>. However,
<literal>'1.5 week'</literal> or <literal>'01:02:03.45'</literal>. Such input is because interval internally stores only three integer units (months,
converted to the appropriate number of months, days, and seconds days, microseconds), fractional units must be spilled to smaller
for storage. When this would result in a fractional number of units. Fractional parts of units greater than months is truncated to
months or days, the fraction is added to the lower-order fields be an integer number of months, e.g. <literal>'1.5 years'</literal>
using the conversion factors 1 month = 30 days and 1 day = 24 hours. becomes <literal>'1 year 6 mons'</literal>. Fractional parts of
For example, <literal>'1.5 month'</literal> becomes 1 month and 15 days. weeks and days are computed to be an integer number of days and
Only seconds will ever be shown as fractional on output. microseconds, assuming 30 days per month and 24 hours per day, e.g.,
<literal>'1.75 months'</literal> becomes <literal>1 mon 22 days
12:00:00</literal>. Only seconds will ever be shown as fractional
on output.
</para> </para>
<para> <para>
@ -2762,10 +2765,10 @@ P <optional> <replaceable>years</replaceable>-<replaceable>months</replaceable>-
<para> <para>
Internally <type>interval</type> values are stored as months, days, Internally <type>interval</type> values are stored as months, days,
and seconds. This is done because the number of days in a month and microseconds. 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 varies, and a day can have 23 or 25 hours if a daylight savings
time adjustment is involved. The months and days fields are integers time adjustment is involved. The months and days fields are integers
while the seconds field can store fractions. Because intervals are while the microseconds field can store fractional seconds. Because intervals are
usually created from constant strings or <type>timestamp</type> subtraction, usually created from constant strings or <type>timestamp</type> subtraction,
this storage method works well in most cases, but can cause unexpected this storage method works well in most cases, but can cause unexpected
results: results: