Discussion:
[ADMIN] about encoding
(too old to reply)
superman0920
2012-03-29 03:22:36 UTC
Permalink
hello
i want to insert a report to postgresql£¬the report contain something Chinese characters and the postgresql is utf-8.

the response from db is this:
ERROR: invalid byte sequence for encoding "UTF8": 0xb1

how can i fix it ?

thx




superman0920
Kevin Grittner
2012-03-29 14:37:12 UTC
Permalink
i want to insert a report to postgresql,the report contain
something Chinese characters and the postgresql is utf-8.
ERROR: invalid byte sequence for encoding "UTF8": 0xb1
That's not a valid byte sequence for a character under the UTF8
character encoding scheme. You said that PostgreSQL is using utf-8,
but what encoding is used for the report? Is your client connecting
using the character encoding scheme used by the report?

-Kevin
--
Sent via pgsql-admin mailing list (pgsql-***@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
amador alvarez
2012-03-30 00:10:11 UTC
Permalink
Hi there,
I am trying to find any kind of information or examples to deal with
custom conflict resolution on swap syncs in a master-master replication.

Any clue will be very wellcome,

Thanks in advance,

Amador A.
--
Sent via pgsql-admin mailing list (pgsql-***@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Kevin Grittner
2012-04-02 18:57:42 UTC
Permalink
Post by amador alvarez
I am trying to find any kind of information or examples to deal
with custom conflict resolution on swap syncs in a master-master
replication.
What are you using for replication?

-Kevin
--
Sent via pgsql-admin mailing list (pgsql-***@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
amador alvarez
2012-04-02 19:58:54 UTC
Permalink
What are you using for replication?

-Kevin


Hi Kevin,

I set up a master-master asynchronous replication of one database with bucardo 4.4.5 and testing right now 4.99.3.
I know the standard settings when a conflict between same id rows comes up :

source - the rows on the "source" database always "win" (in a conflict, we copy rows from source to target)


target - the rows on the "target" database always win


skip - any conflicted rows are simply not replicated. Not recommended
for most cases.


random - each database has an equal chance of winning each time


latest - the row that was most recently changed wins


abort - the sync is aborted on a conflict You can also provide custom
conflict handlers to allow you to use business logic for better conflict
resolution.


I have not found info or examples about the custom option yet, and still on the search ...

Cheers,

Amador A.
Post by Kevin Grittner
Post by amador alvarez
I am trying to find any kind of information or examples to deal
with custom conflict resolution on swap syncs in a master-master
replication.
What are you using for replication?
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-***@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Loading...