Andreas Kostyrka wrote:
> 
> Some questions/hints:
> 
> 1.) What versions of PG are you running? Some version of PG (I think it
> was 8.2, but I'd had to check that) has become much more exact in
> processing UTF-8. If you are replicating from an PG version that is
> older than the version on the slaves this could be it.
> 

 The Master is running PG version 8.1.5 as a server but 8.2 as the client
querying interface (the psql reports 8.2 as its version but 8.1.5 as the
server version). I dont understand why or how the DB admin managed to set it
up that way on the Redhat Enterprise (RHEL 4) but thats what I have to work
with
  The Slave is PG 8.2.6 on OpenSuSE 10.3 but both slony are the same
(1.2.12)



> 2.) the client encoding is not much of an issue here, what is your
> server encoding?
> 
> 
  The Master server encoding is also UTF-8 (same as the Slave) and I started
the replication right after using the SET client_encoding command.
  I considered replacing the version of the postgresql on the Slave with the
same version on the Master but the issue is "Which one do I install? 8.1.5
or 8.2?" and "Shouldn't there be another solution that would not affect the
data on the other DBs on the Slave?"

   Victor

-- 
View this message in context: http://www.nabble.com/UTF-8-encoding-Error-tp16000710p16023017.html
Sent from the Slony-I -- General mailing list archive at Nabble.com.