pg_dump and client_encoding

Started by Jan Poslusnyover 22 years ago4 messagesgeneral
Jump to latest
#1Jan Poslusny
pajout@gingerall.cz

I have following experience:
After pg_dump mydb > db.out output contains one or more \connect -
somebody, but client_encoding is not set. It causes restoration problems
on databases with different default client_encoding. I think
client_encoding may be set after each \connect.

#2Peter Eisentraut
peter_e@gmx.net
In reply to: Jan Poslusny (#1)
Re: pg_dump and client_encoding

Jan Poslusny wrote:

I have following experience:
After pg_dump mydb > db.out output contains one or more \connect -
somebody, but client_encoding is not set. It causes restoration
problems on databases with different default client_encoding. I
think client_encoding may be set after each \connect.

The client_encoding parameter specifies to the server what encoding the
client uses. Presumably, that stays the same during one psql run.

Maybe you haven't set the client encoding at all? Try setting the
environment variable PGCLIENTENCODING. Else, please post a more
specific description of the symptoms of your problem.

#3Karam Chand
karam_chand03@yahoo.com
In reply to: Peter Eisentraut (#2)
C API Documentation

Hello

Is there any link where I can get all the
documentation about C API for PostgreSQl in one page.
I would love to take a printout of it and use it for
reference.

Karam

__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus

#4Venkatesh R Ramteke
ramteke@cse.iitb.ac.in
In reply to: Karam Chand (#3)
unsubscribe pgsql-general

unsubscribe pgsql-general