PostgreSQL supports the use of 64-bit integer values for date/time types instead of the default double. This option is not yet offered by the port Makefiles. The supplied patch adds support for this feature to the postgresql74-server port. Fix: . if defined(SERVER_ONLY) && defined(WITH_PAM) CONFIGURE_ARGS+=--with-pam @@ -114,10 +113,6 @@ INSTALL_TARGET= install . else INSTALL_TARGET= install-strip -. endif - -. if defined(WITH_INTDATE) -CONFIGURE_ARGS+= --enable-integer-datetimes . endif . if defined(WITH_MIT_KRB5)--cl8xnjB2ws2PEjUxgcZbLumfFk7u3V4NAekWGzhM0yBgSgRK Content-Type: text/plain; name="file.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="file.diff" --- /usr/ports/databases/postgresql74-server/Makefile Wed Feb 2 11:55:57 2005 +++ /usr/ports/databases/postgresql74-server/Makefile.orig Wed Feb 2 11:59:39 2005 @@ -86,7 +86,6 @@ OPTIONS+= TESTS "Allows the use of a \"check\" target" off . endif OPTIONS+= DEBUG "Builds with debugging symbols" off -OPTIONS+= INTDATE "Builds with 64-bit integer date/time type" off
Responsible Changed From-To: freebsd-ports-bugs->girgen Over to maintainer.
Well, it would add that support, but the patch obviously is reversed. I can't understand how that happened. I'm sorry. -- Christian Ullrich
Changing this will require a dump/restore... There must be some sort of warning about this in the port. Have you any idea why it is not on by default? Fresh code, not as well tested? /Palle
> Have you any idea why it is not on by default? Fresh code, not as well > tested? No, it's been in there since 7.3. The reason is that timestamps stored as doubles degrade in precision with increasing distance from "zero", as the exponent rises and significant digits are lost. It's in the PostgreSQL docs, in "Date/Time Types". Storing them as integer values, however, avoids that, at the price of a limited range. Limited, that is, to 290000 years into the future. -- Christian Ullrich
--On torsdag, februari 03, 2005 19.58.25 +0100 Christian Ullrich <chris@chrullrich.de> wrote: >> Have you any idea why it is not on by default? Fresh code, not as well >> tested? > > No, it's been in there since 7.3. The reason is that timestamps > stored as doubles degrade in precision with increasing distance > from "zero", as the exponent rises and significant digits are lost. > It's in the PostgreSQL docs, in "Date/Time Types". > > Storing them as integer values, however, avoids that, at the price > of a limited range. Limited, that is, to 290000 years into the > future. heh :-) Well, that's probably enough for most ppl. But it's cool to have a timestamp that goes on forever, but with less precision. It is a very good idea, indeed :)
State Changed From-To: open->closed Committed. Thanks!