From: Ben K. <bkim@coe.tamu.edu>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: encoding question
Date: Tue, 21 Mar 2006 14:14:14 -0600 (CST)
Message-ID: <Pine.GSO.4.64.0603211402560.24850@coe.tamu.edu> (raw)
In-Reply-To: <Pine.GSO.4.64.0603211015260.16852@coe.tamu.edu>
References: <Pine.GSO.4.64.0603201643250.21796@coe.tamu.edu>
<9058.1142898110@sss.pgh.pa.us>
<Pine.GSO.4.64.0603211015260.16852@coe.tamu.edu>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: bkim@coe.tamu.edu, tgl@sss.pgh.pa.us
Subject: Re: encoding question
In-Reply-To: <Pine.GSO.4.64.0603211402560.24850@coe.tamu.edu>
References: <Pine.GSO.4.64.0603201643250.21796@coe.tamu.edu> <9058.1142898110@sss.pgh.pa.us> <Pine.GSO.4.64.0603211015260.16852@coe.tamu.edu> <Pine.GSO.4.64.0603211402560.24850@coe.tamu.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox