From: | a <372660931(at)qq(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Does pgAgent support chinese, japanese characters? |
Date: | 2018-06-13 01:20:49 |
Message-ID: | tencent_0A9BB3CE40FEEC222977EFBA@qq.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks a lot for your reply.
I tried to set the host/client encoding, however, when I create new tables using Chinese, it reported an encoding error...... also with other queries.....
May I ask encoding of pgAgent? May it reading from a text file? Or I can use notepad++ to convert and then copy??
------------------ Original ------------------
From: "Tom Lane";
Date: Tuesday, Jun 12, 2018 9:59 PM
To: "a"<372660931(at)qq(dot)com>;
Cc: "pgsql-general";
Subject: Re: Does pgAgent support chinese, japanese characters?
"=?ISO-8859-1?B?YQ==?=" <372660931(at)qq(dot)com> writes:
> Hi I'm using pgAgent to set up daily or monthly tasks.
> I have tables that with the name of Chinese or Japanese. It runs ok in normal sql script, but report non-recognizable in pgAgent SQL jobs.
First guess is that client_encoding is getting set differently in the
pgAgent-initiated sessions than elsewhere, causing incorrect character set
conversions to happen.
> I'm using windows server 2008, pgsql 10, and pgAgent 3.4, may there be a way of supporting different languages??
... unfortunately, I don't know anything about how to adjust that
in Windows. A brute-force way would be to issue "set client_encoding"
in your scripts, but there may be a better way.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2018-06-13 02:43:27 | Re: Logging |
Previous Message | Andres Freund | 2018-06-13 00:39:22 | Re: Print pg_lsn as a number? |