From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "fkater(at)googlemail(dot)com" <fkater(at)googlemail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: integer_datetime: 8.2/8.4 differences ? |
Date: | 2010-03-15 19:15:31 |
Message-ID: | 22113.1268680531@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"fkater(at)googlemail(dot)com" <fkater(at)googlemail(dot)com> writes:
> I updated the server from 8.2 to 8.4, but I am still using
> libpq 8.2 to write timestamps with the libpq C interface,
> using the binary format and PQexecParams(). While pgAdmin in
> 8.2 server shows correct timestamps, 8.4 displays garbage
> (year 15000 etc).
> This has probably to do with the compile time option
> integer_datetime -- however, did anything change? I could
> not find anything in the changelogs.
The first item listed under "Observe the following incompatibilities"
in the 8.4 release notes is
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Vick Khera | 2010-03-15 19:27:38 | Re: hardware for a server |
Previous Message | Bruce Momjian | 2010-03-15 19:02:42 | Re: hardware for a server |