From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Glaesemann <grzm(at)myrealbox(dot)com> |
Cc: | pgsql-patches Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: --enable-integer-datetimes doc patch |
Date: | 2005-06-12 15:53:52 |
Message-ID: | 24606.1118591632@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Michael Glaesemann <grzm(at)myrealbox(dot)com> writes:
> I can't seem to find any documentation on the --enable-integer-
> datetimes configure option. Here's a patch that adds a very brief
> description to section 14.5 Installation Procedure, which lists the
> other config options.
Well, there is some, but I agree that it ought to be mentioned where
the other config options are listed. Applied with additions, viz
*** doc/src/sgml/installation.sgml.orig Sun Jun 5 00:59:44 2005
--- doc/src/sgml/installation.sgml Sun Jun 12 11:49:15 2005
***************
*** 874,879 ****
--- 874,894 ----
</varlistentry>
<varlistentry>
+ <term><option>--enable-integer-datetimes</option></term>
+ <listitem>
+ <para>
+ Use 64-bit integer storage for datetimes and intervals, rather
+ than the default floating-point storage. This reduces the range
+ of representable values but guarantees microsecond precision across
+ the full range (see <xref linkend="datatype-datetime"> for more
+ information). Note also that the integer datetimes code is newer
+ than the floating-point code, and we still find bugs in it from time
+ to time.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
<term><option>--disable-spinlocks</option></term>
<listitem>
<para>
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-06-12 18:50:58 | Re: BUG #1707: statistics collector starts with stats_start_collector = false |
Previous Message | Michael Glaesemann | 2005-06-12 13:41:47 | --enable-integer-datetimes doc patch |