From: | "Dan Langille" <dan(at)langille(dot)org> |
---|---|
To: | Sean Chittenden <sean(at)chittenden(dot)org> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: 7.1->7.2 data import timestamp problems |
Date: | 2002-02-23 19:28:47 |
Message-ID: | 200202231928.g1NJSuk43520@lists.unixathome.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 23 Feb 2002 at 11:22, Sean Chittenden wrote:
> > I've just been able to confirm that 7.1.2 can import the above data. My
> > plans for 7.2 are now on hold while I try to find a way to get 7.2 to
> > accept the data that has been exported from 7.1.
>
> perl -p -i -e 's#current#now#igo' pgsql_dump.sql
>
> Double check that you don't have the word 'current' in your dump other than
> timestamps.
>
> grep -i current pgsql_dump.sql
>
> HTH -sc
Sean: you are on the same track I am. Yes, I found 9 such values in a
timestamp field. I corrected the data, exported, and imported into 7.2.
All went well[1].
Now my concern is how the value 'current' found its way into a timestamp
field.... I'm looking at the application.
thank you.
[1] - I did have to manually modify the pg_dump output to remove the
quotes from around current_timestamp (as mentioned elsewhere).
--
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/ - practical examples
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Langille | 2002-02-23 19:44:04 | Re: 7.1->7.2 data import timestamp problems |
Previous Message | Sean Chittenden | 2002-02-23 19:22:30 | Re: 7.1->7.2 data import timestamp problems |