Re: [GENERAL] client_encoding / postgresql strange behaviour

2008-09-16 Thread Michael Fuhr
On Tue, Sep 16, 2008 at 05:15:41AM -0600, Enrico Sabbadin wrote: > Hi, as far as I've understood client_encoding tells postgresql > how data "will arrive / must be send back" to the client application. > Postgresql will do the conversion for you if the database encoding is > different. Correct

Re: [GENERAL] client_encoding

2008-02-21 Thread Dean Gibson (DB Administrator)
On 2008-02-21 19:59, Tom Lane wrote: You can set client_encoding in postgresql.conf if you want to, but I'm having a hard time understanding why you think that'd be a good idea --- *particularly* if your database encodings aren't all the same. regards, tom lane Act

Re: [GENERAL] client_encoding

2008-02-21 Thread Tom Lane
"Dean Gibson (DB Administrator)" <[EMAIL PROTECTED]> writes: > If I "ALTER DATABASE ... SET client_encoding TO DEFAULT", is the default > the "client_encoding" in postgresql.conf when the server was last > started, or the value at the time the "ALTER DATABASE ... SET > client_encoding TO DEFAULT

[GENERAL] client_encoding

2008-02-21 Thread Dean Gibson (DB Administrator)
If I "ALTER DATABASE ... SET client_encoding TO DEFAULT", is the default the "client_encoding" in postgresql.conf when the server was last started, or the value at the time the "ALTER DATABASE ... SET client_encoding TO DEFAULT" statement is executed? In other words, if I "ALTER DATABASE ... S

Re: [GENERAL] client_encoding error

2007-11-28 Thread Albe Laurenz
Glyn Astill wrote: > Whilst trying to migrate one of our tables to postgres we get the > following error: > > invalid byte sequence for encoding "EUC_JP" : 0x9c32 > HINT: This error can also happen if the byte sequence does not match > the enccding expected by the server, which is controlled by "c

[GENERAL] client_encoding error

2007-11-27 Thread Glyn Astill
Whilst trying to migrate one of our tables to postgres we get the following error: invalid byte sequence for encoding "EUC_JP" : 0x9c32 HINT: This error can also happen if the byte sequence does not match the enccding expected by the server, which is cont roll

Re: [GENERAL] client_encoding values

2005-12-16 Thread Bruce Momjian
wrote: > Hello! > > Please, help. I need to get complete list of 'client_encoding' > values supported by the PostgreSQL Server. Can I somehow get these > values using select query or function call? Uh, we have a pg_conversion table, but I don't know how to tell which are av

[GENERAL] client_encoding values

2005-12-12 Thread Андрей
Hello! Please, help. I need to get complete list of 'client_encoding' values supported by the PostgreSQL Server. Can I somehow get these values using select query or function call? Best regards, Kovalevski Andr

Re: [GENERAL] client_encoding

2000-09-06 Thread Tatsuo Ishii
> How do I get rid of this error? > > Unrecognized variable client_encoding > > It is repeated with every psql command. The message indicates the backend has been compiled without --enable-multibyte option, but your frontend has been made with the option. I guess you have mixed up two dif