By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,708 Members | 2,080 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,708 IT Pros & Developers. It's quick & easy.

pg_dump and client_encoding

P: n/a
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.
---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
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.
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Nov 12 '05 #2

P: n/a
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

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Nov 12 '05 #3

P: n/a
unsubscribe pgsql-general


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.