| Lists: | pgsql-general |
|---|
| From: | Jan Ploski <jpljpl(at)gmx(dot)de> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Unicode database + JDBC driver performance |
| Date: | 2002-12-21 17:13:28 |
| Message-ID: | 2523214.1040490808814.JavaMail.jpl@remotejava |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Lists: | pgsql-general |
On Sat, Dec 21, 2002 at 11:45:08AM -0500, Tom Lane wrote:
> Jan Ploski <jpljpl(at)gmx(dot)de> writes:
> > The Unicode database is slower both on INSERTs and especially on
> > SELECTs.
>
> What did you have PGCLIENTENCODING set to in each case? I am wondering
> if you were incurring an extra conversion ...
Tom,
When connecting to the Unicode database, I did not use any 'charSet'
parameter for the JDBC driver (which I assume translates to
PGCLIENTENCODING on the backend?). When I specified charSet=UNICODE,
I got an exception when executing the query. Without, it worked fine.
For the LATIN1 database, I used charSet=LATIN1 in driver's connection
string. It worked as expected (the conversion of non-ASCII characters
was not correct, but that's ok).
Is there some other way to find out what PGCLIENTENCODING is used
in each case?
Take care -
JPL
| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Ploski <jpljpl(at)gmx(dot)de> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Unicode database + JDBC driver performance |
| Date: | 2002-12-21 19:57:51 |
| Message-ID: | [email protected] |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Lists: | pgsql-general |
Jan Ploski <jpljpl(at)gmx(dot)de> writes:
> Is there some other way to find out what PGCLIENTENCODING is used
> in each case?
I think "show client_encoding" and "show server_encoding" would tell
what you want (not sure how well JDBC cooperates with the SHOW command
though).
regards, tom lane