Обсуждение: Migration from ASCII to UTF8

ASCII character encoding means that the database does not care about the
encoding. So it is the responsibility of the programs you use, to use the
correct encoding for your application. So you need to know the used encoding
of your applications/data in your database. Then you can convert a text
backup by recode, iconv or anything like that to utf8. You should be able to
restore the corrected dump  into a utf8 database. If your applications used
different encodings you have to fix this somehow by hand first.

In chapter 22 of the manual you can find more details about encodings.

Best regards
Ivo

Am Freitag, 30. Mai 2008 15:45:25 schrieb Campbell, Lance:
> I have a database that is in ASCII character encoding.  How do I go
> about migrating it to UTF8?
>
>
>
> Thanks,
>
>
>
> Lance Campbell
>
> Project Manager/Software Architect
>
> Web Services at Public Affairs
>
> University of Illinois
>
> 217.333.0382
>
> http://webservices.uiuc.edu
>
> My e-mail address has changed to lance@illinois.edu

 Hi,


We have an issue with a database on IP SAN disks (Solaris x64), where
some tables and indexes got corrupted, apparently in correlation with
the use of forcedirectio in the nfs for data and indexes:

   ERROR:  unexpected data beyond EOF in block ...
   HINT:   This has been seen to occur with buggy kernels; consider
updating your system.

Now I'm interested in a way to get the list of all corrupted objects.
The only way I know is to check the errors of pg_dump or vacuum.
Is there a faster way, something like "vacuum check_only" ?

Thanks,

Marc Mamin