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

suggestion for "psql"

P: n/a
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi there,

I haven't found a way to set the client encoding of a psql connection other
then "\encoding" which is arkward for batch processing. As .psqlrc is being
ignored during batch processing and the internal encoding is being set
*after* "-v", I have to resort to arkward solutions in order to read data via
scripts. (To whom it may concern: instead of using "-c" you can pipe your
command from stdin).

Shouldn't psql honour the current locale setting (LC_CTYPE) or/and have a
command line option to set the encoding?

Mit freundlichem Gruß / With kind regards
Holger Klawitter
- --
lists <at> klawitter <dot> de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFBmGry1Xdt0HKSwgYRAgBYAJ4yxnCSDn3MgTvuLUs8t/bffC7HDwCeMDr2
j8np4ISSUI5AvjQE30AfvCM=
=4f1P
-----END PGP SIGNATURE-----

---------------------------(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 23 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Holger Klawitter wrote:
Shouldn't psql honour the current locale setting (LC_CTYPE) or/and
have a command line option to set the encoding?


The environment variable PGCLIENTENCODING serves this purpose.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to ma*******@postgresql.org)

Nov 23 '05 #2

P: n/a
Holger Klawitter wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi there,

I haven't found a way to set the client encoding of a psql connection other
then "\encoding" which is arkward for batch processing. As .psqlrc is being
ignored during batch processing and the internal encoding is being set
*after* "-v", I have to resort to arkward solutions in order to read data via
scripts. (To whom it may concern: instead of using "-c" you can pipe your
command from stdin).


set client_encoding=MyEncoding;

--
Richard Huxton
Archonet Ltd

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Nov 23 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.