That makes sense, of course. I'm guessing this is because I formally used the pgInstaller and since 8.4 is not supported yet by pgInstaller I moved to the EnterpriseDB installer. The man behind the current must have done the build with different options. Would you concur? Maybe I should ask the man behind the curtain (Dave Page).
Thanks! -----Original Message----- From: Tom Lane [mailto:t...@sss.pgh.pa.us] Sent: Wednesday, October 14, 2009 10:21 AM To: Chase, John Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] COPY BINARY 8.3 to 8.4 timestamp incorrect "Chase, John" <jch...@mtcsc.com> writes: > I am working on upgrading from 8.3.7 to 8.4.1. One of the functions of > our application is to "export" and "import" data, and to accomplish this > I've written some functions that use COPY ... TO ... BINARY and COPY ... > FROM ... BINARY. In testing the upgrade to 8.4.1 I noticed that when I > "import" from export files that were created under 8.3.7 the timestamps > are not brought in correctly. Probably you've got 8.4 compiled with integer timestamps where the 8.3 DB used float timestamps, or perhaps vice-versa. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
