From: | digoal <digoal(at)126(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: BUG #9210: PostgreSQL string store bug? not enforce check with correct characterSET/encoding |
Date: | 2014-02-14 01:55:07 |
Message-ID: | 7ab78936.17ace.1442e1abb73.Coremail.digoal@126.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
HI,
Thanks very much.
We use dblink or foreign table migrate datas instead pg_dump now resolve the error data load problem.
--
公益是一辈子的事,I'm Digoal,Just Do It.
At 2014-02-14 04:49:08,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>digoal(at)126(dot)com writes:
>> select t, t::bytea from convert_from('\xeec1', 'sql_ascii') as g(t);
>> [ fails to check that string is valid in database encoding ]
>
>Hm, yeah. Normal input to the database goes through pg_any_to_server(),
>which will apply a validation step if the source encoding is SQL_ASCII
>and the destination encoding is something else. However, pg_convert and
>some other places call pg_do_encoding_conversion() directly, and that
>function will just quietly do nothing if either encoding is SQL_ASCII.
>
>The minimum-refactoring solution to this would be to tweak
>pg_do_encoding_conversion() so that if the src_encoding is SQL_ASCII but
>the dest_encoding isn't, it does pg_verify_mbstr() rather than nothing.
>
>I'm not sure if this would break anything we need to have work,
>though. Thoughts? Do we want to back-patch such a change?
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | eshkinkot | 2014-02-14 16:31:25 | BUG #9223: plperlu result memory leak |
Previous Message | Greg Stark | 2014-02-14 01:06:13 | Re: some postgres 2s SELECT queries are deadlocking forever in __sendto (libsystem_kernel.dylib) |
From | Date | Subject | |
---|---|---|---|
Next Message | Jerry Sievers | 2014-02-14 02:24:27 | HBA files w/include support? |
Previous Message | Haribabu Kommi | 2014-02-14 01:19:56 | Re: Per table autovacuum vacuum cost limit behaviour strange |