pg_dump and client_encoding

[Jan Poslusny]

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

[Peter Eisentraut]

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

[Karam Chand]

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

[Venkatesh R Ramteke]

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