| From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
|---|---|
| To: | Doug Kunzman <dkunzman(at)usgs(dot)gov> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: character encoding |
| Date: | 2012-12-06 15:30:44 |
| Message-ID: | 50C0BA24.7010806@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/06/2012 07:20 AM, Doug Kunzman wrote:
> I'm trying to support an automatic character encoding to UNICODE so Java
> strings with none ASCII character can be stored in a table.
>
> I've edited my postgressql.conf with the following command,
> PGCLIENTENCODING=UNICODE
>
> And I'm getting this error message,
>
> FATAL: unrecognized configuration parameter "PGCLIENTENCODING"
>
> Any ideas? your help would be appreciated.
client_encoding (string)
Sets the client-side encoding (character set). The default is to
use the database encoding. The character sets supported by
the PostgreSQL server are described in Section 22.3.1.
I believe PGCLIENTENCODING is the env setting.
>
> Thanks, doug
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Glenn Pierce | 2012-12-06 18:31:26 | Re: Trigger / constraint issue |
| Previous Message | Doug Kunzman | 2012-12-06 15:20:00 | character encoding |