cvs commit: ports/databases/postgresql84-client Makefile ports/databases/postgresql84-server Makefile distinfo pkg-plist-client pkg-plist-server ports/databases/postgresql84-server/files patch-src:backend:utils:misc:postgresql.conf.sample

[Martin Matuska]

For your information, INTDATE was already on, even if not set.

>From The PostgreSQL 8.4.0 HISTORY:

     * Use 64-bit integer datetimes by default (Neil Conway)
       Previously this was selected by configure's
       "--enable-integer-datetimes" option. To retain the old behavior,
       build with "--disable-integer-datetimes".  

This behaivior was not implemented in the 8.4.0 port, so:

- if INTDATE was set, the 8.4.0 port used the configure argument
"--enable-integer-datetimes" (which was deprecated and replaced by
--disable-integer-datetimes)
- ff INTDATE was not set, the 8.4.0 port just used no configure argument
related to integer datetime - and that means, INTDATE was on, anyway.

So independent of the INTDATE setting the port always used 64-bit
integer datetimes. The binary packages remain compatible.

Larry Rosenman  wrote / napísal(a):
> Setting INTDATE on by default means folks can't just do a binary upgrade.
> They need to pg_dump/pg_restore.
>
> IMHO this should NOT happen on a .0 -> .1 port change.
>