> Hard to believe it's a pg_dump bug.
You are right, Yudit shows an invalid UTF-8 character.
For example, record OID 20643 has invalid =E3=82 character. But, when
querying the PostgreSQL 7.1.3 database, I can see the missing character which
displays well in Apache/PHP.
It seems to be a pg_dump bug or a peculiar kind of UTF-8 (is there any
difference between Windows / Unix ?). There are hundreds of errors in the
complete dump. But the data displays always well.
How can I test the database further in psql or in PHP. I would like to query
record OID 20643 and see if E3/82 is there or not. Any idea how to proceed?
Thank you very much for your help.
In response to
pgsql-hackers by date
|Next:||From: Stephan Szabo||Date: 2002-02-20 16:24:32|
|Subject: Re: pg_type defaults|
|Previous:||From: Stephan Szabo||Date: 2002-02-20 16:02:53|
|Subject: Re: pg_dump: use ALTER TABLE for PKs|
pgsql-odbc by date
|Next:||From: Tom Lane||Date: 2002-02-20 17:04:29|
|Subject: Re: [ODBC] UTF-8 data migration problem in Postgresql 7.2 |
|Previous:||From: Kristis Makris||Date: 2002-02-20 15:36:28|
|Subject: Re: Are multiple selects of the same field allowed|