Re: [GENERAL] Still big problems with pg_dump!

Tom Lane wrote:

>Wim <wdh(at)belbone(dot)be> writes:
>
>>>Hm. Are you running in a multibyte character encoding? I had a note
>>>that make_greater_string may have problems in the MULTIBYTE case.
>>>
>
>>Yes, I compiled postgres with multibyte and ODBC support .
>>
>
>But are you actually *using* the multibyte code? What does "psql -l"
>show as the encoding for your database?
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 5: Have you checked our extensive FAQ?
>
>http://www.postgresql.org/users-lounge/docs/faq.html
>
>
>
psql -l shows:

List of databases
Name | Owner | Encoding
---------------+----------+-----------
addressIP | postgres | SQL_ASCII
belbonedb_v2 | postgres | SQL_ASCII
belbonedb_v21 | postgres | SQL_ASCII
peering | postgres | SQL_ASCII
peering_v2 | postgres | SQL_ASCII
postgres | postgres | SQL_ASCII
smsbilling | postgres | SQL_ASCII
template0 | postgres | SQL_ASCII
template1 | postgres | SQL_ASCII
(9 rows)

Maybe I should recompile Postgres without multibyte support...

Cheers!

Wim