From owner-freebsd-database Sat Feb 23 13: 5:26 2002 Delivered-To: freebsd-database@freebsd.org Received: from primus.vsservices.com (primus.vsservices.com [63.66.136.75]) by hub.freebsd.org (Postfix) with ESMTP id B504637B423; Sat, 23 Feb 2002 13:05:16 -0800 (PST) Received: from prime.vsservices.com (conr-adsl-dhcp-26-38.txucom.net [209.34.26.38]) by primus.vsservices.com (8.11.3/8.11.3) with SMTP id g1NHsEk88727; Sat, 23 Feb 2002 11:54:14 -0600 (CST) (envelope-from gclarkii@vsservices.com) Date: Sat, 23 Feb 2002 11:54:17 -0600 From: GB Clark To: dan@langille.org Cc: freebsd-questions@FreeBSD.ORG, freebsd-database@FreeBSD.ORG Subject: Re: postgresql 7.1->7.2 data import timestamp problems Message-Id: <20020223115417.1b750f1d.gclarkii@vsservices.com> In-Reply-To: <200202231727.g1NHRYk42516@lists.unixathome.org> References: <200202231727.g1NHRYk42516@lists.unixathome.org> X-Mailer: Sylpheed version 0.6.6 (GTK+ 1.2.10; i386-unknown-freebsd4.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-database@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 23 Feb 2002 12:27:32 -0500 "Dan Langille" wrote: > Just a heads up in case anyone is planning to upgrade to postgresql 7.2. > I've found a few problems. The major problem, which is preventing me from > upgrading is: > > $ psql fp2migration < fp2migration.sql > [snip] > ERROR: copy: line 2537, Bad timestamp external representation 'current' > lost synchronization with server, resetting connection > ^C > > Until I get that solved, I'll be staying on 7.1.2. I spent several hours > on this already and have found no solution. > > This is definitly a migration issue as 7.1.2 accepts the data but 7.2 does > not. > -- > Dan Langille > The FreeBSD Diary - http://freebsddiary.org/ - practical examples Dan, This has been discussed on the PostgreSQL lists. It has something to due with all of the time/date changes between 7.1.? and 7.2. Check the archives for a cure. But I'm willing to bet that your using current to set a timestamp to a default time/date, right? You might try current_timestamp() instead and make sure it is not in quotes. I ran into a like problem after using timestamp as a field name...:) Not good. GB -- GB Clark II | Roaming FreeBSD Admin gclarkii@VSServices.COM | General Geek CTHULU for President - Why choose the lesser of two evils? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-database" in the body of the message