Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
0f6be37f
Commit
0f6be37f
authored
20 years ago
by
Tom Lane
Browse files
Options
Downloads
Patches
Plain Diff
Clarify that the --enable-integer-datetimes switch affects the time and
interval datatypes as well as timestamp.
parent
be105bd7
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/src/sgml/datatype.sgml
+9
-5
9 additions, 5 deletions
doc/src/sgml/datatype.sgml
with
9 additions
and
5 deletions
doc/src/sgml/datatype.sgml
+
9
−
5
View file @
0f6be37f
<!--
$PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.15
3
2005/01/
08 05:19
:1
8
tgl Exp $
$PostgreSQL: pgsql/doc/src/sgml/datatype.sgml,v 1.15
4
2005/01/
17 18:47
:1
5
tgl Exp $
-->
<chapter id="datatype">
...
...
@@ -1351,7 +1351,7 @@ SELECT b, char_length(b) FROM test2;
<entry>time intervals</entry>
<entry>-178000000 years</entry>
<entry>178000000 years</entry>
<entry>1 microsecond</entry>
<entry>1 microsecond
/ 14 digits
</entry>
</row>
<row>
<entry><type>date</type></entry>
...
...
@@ -1367,7 +1367,7 @@ SELECT b, char_length(b) FROM test2;
<entry>times of day only</entry>
<entry>00:00:00.00</entry>
<entry>23:59:59.99</entry>
<entry>1 microsecond</entry>
<entry>1 microsecond
/ 14 digits
</entry>
</row>
<row>
<entry><type>time [ (<replaceable>p</replaceable>) ] with time zone</type></entry>
...
...
@@ -1375,7 +1375,7 @@ SELECT b, char_length(b) FROM test2;
<entry>times of day only, with time zone</entry>
<entry>00:00:00.00+12</entry>
<entry>23:59:59.99-12</entry>
<entry>1 microsecond</entry>
<entry>1 microsecond
/ 14 digits
</entry>
</row>
</tbody>
</tgroup>
...
...
@@ -1410,7 +1410,11 @@ SELECT b, char_length(b) FROM test2;
eight-byte integers (a compile-time
option), microsecond precision is available over the full range of
values. However eight-byte integer timestamps have a more limited range of
dates than shown above: from 4713 BC up to 294276 AD.
dates than shown above: from 4713 BC up to 294276 AD. The same
compile-time option also determines whether <type>time</type> and
<type>interval</type> values are stored as floating-point or eight-byte
integers. In the floating-point case, large <type>interval</type> values
degrade in precision as the size of the interval increases.
</para>
</note>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment