Re: Mixed client_encoding database question - Mailing list pgsql-general

From Alban Hertroys
Subject Re: Mixed client_encoding database question
Date
Msg-id 203CD732-E69B-44E8-8DC0-D99093A7E53A@solfertje.student.utwente.nl
Whole thread Raw
In response to Mixed client_encoding database question  ("J. Hondius" <jhondius@rem.nl>)
List pgsql-general
On 10 Jan 2011, at 16:32, J. Hondius wrote:

> Hi all,
>
> We have a product  with a PostgreSQLdatabase (unicode)
> It has a (legacy) client app that uses client_encoding = win1521
> The legacy app will be around for several years.
> It cannot change to unicode.
>
> There also is a new client app, written in java.
> It uses client_encoding = unicode.


I think you may be able to set the client encoding at the user level. In that case you could use a different user for
thelegacy app than you use for the java app and have the appropriate client encoding for both cases. 

try: ALTER ROLE foo SET client_encoding TO 'win1251';

Note: This is just off the top of my head, I haven't actually verified any of this.

Alban Hertroys

--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.


!DSPAM:737,4d2c9b0a11871070112136!



pgsql-general by date:

Previous
From: "Karayappalli, Raghunath (Raghu)"
Date:
Subject: Re: database is growing... 1GB per day basis
Next
From: "Karayappalli, Raghunath (Raghu)"
Date:
Subject: Re: database is growing... 1GB per day basis