| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ruzsinszky Attila <ruzsinszky(dot)attila(at)gmail(dot)com> |
| Cc: | pgsql-novice(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org, Joe Conway <mail(at)joeconway(dot)com> |
| Subject: | Re: [NOVICE] LATIN2->UTF8 conversation with dblink |
| Date: | 2009-02-02 18:31:54 |
| Message-ID: | 23494.1233599514@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-novice |
Ruzsinszky Attila <ruzsinszky(dot)attila(at)gmail(dot)com> writes:
> The situation:
> We've got two machines. The source database (DB) is running on an RHEL
> 5.x machine
> with PSQL 8.1.11. The destination DB is running on SuSE 11.0 with PSQL 8.3.x.
> The mechines are relative far away each other and there is a 2Mbps WAN
> line between them.
> The DB is the same except the character coding. Source is LATIN2 and
> the target DB is UTF8.
> We wrote a trigger to copy the data from source to target with dblink.
> The problem is the
> different DB character coding! PGSQL complains about wrong byte order.
Hmm. You can presumably fix this by setting client_encoding in the
dblink connection to match the encoding in use in the database it's
called in. But I wonder why dblink doesn't just do that for you
automatically.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2009-02-02 19:03:29 | Re: LIMIT NULL |
| Previous Message | Tom Lane | 2009-02-02 18:25:42 | Re: parallel restore |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ries van Twisk | 2009-02-02 19:20:43 | Re: [NOVICE] LATIN2->UTF8 conversation with dblink |
| Previous Message | Ruzsinszky Attila | 2009-02-01 11:04:32 | LATIN2->UTF8 conversation with dblink |