From: | "Ben K(dot)" <bkim(at)coe(dot)tamu(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: encoding question |
Date: | 2006-03-21 20:14:14 |
Message-ID: | Pine.GSO.4.64.0603211402560.24850@coe.tamu.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I just wanted to add that when I created the same database with -E
SQL_ASCII on my linux box, the dump was loaded fine. I created another
database without -E and observed the same invalid encoding problem.
On the face value this seems to solve the problem at least superficially.
I'd like to check the data validity, and the easiest way seems to be to
dump the data again from the linux box and compare with the original.
Is there a way to compare between any two databases online? (like running
a script checking row counts and schema) If I run crc on the concat of all
fields in a row, and if the crc matches, would it be reasonably
sufficient? Is there a stronger validation method?
Thanks.
Ben K.
Developer
http://benix.tamu.edu
From | Date | Subject | |
---|---|---|---|
Next Message | Ivo Rossacher | 2006-03-21 21:38:03 | Re: encoding question |
Previous Message | Vishal Kashyap | 2006-03-21 20:06:23 | Re: Lets Vote |