Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Okay, so I'm migrating Project Open to a new server (opensource project management system built on OpenACS which uses AOLServer) and ran into a very strange issue: importing a 7.4 dump automatically adjusts "timestamp with time zone" values to GMT from GMT+1/+2 (CET), which seriously messes up things since I got a lot of 2009-01-10 00:00:00+02 which turns into 2009-01-09 22:00:00+00 essentially jumping a day back, and that messes up some features. How can I turn off this adjustment feature? Thanks in advance.

For the record the server both the old and the new server is set to CET, not GMT.

Edit: no, I can't use 8.3/8.4.

share|improve this question
up vote 3 down vote accepted

Try exporting using the newer versions of pg_dump or pg_dumpall

I've had a number of odd things arise doing PostgreSQL dumps/restores from/to the versions you've specified. I'm assuming you're moving from RedHat or CentOS 4.x to 5.x. I've found issues with the pg_dump and pg_dumpall output from the CentOS/RHEL 4.x versions. In all cases, my problems were resolved by performing the dump of the old database using a higher version on PostgreSQL.

If your target is the newer server, use that system to run the dump over the network or install a newer version of PostgreSQL (from the 8.1.15 source in /opt, for instance) on the source server in order to use its pg_dump command. See if that resolves the issue.

share|improve this answer
Yes, this solved it, thanks a lot! – KTamas Nov 15 '09 at 21:38

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.