Thu Jun 12 05:26:28 PDT 2008
- Previous message: [Slony1-general] replication set up, but no replication
- Next message: [Slony1-general] table truncation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jeff Davis wrote: > On Wed, 2008-06-11 at 16:14 -0400, Geoffrey wrote: >> I definitely seem some issues with encoding, and from what I see, >> there's database and client encoding. The database encoding is >> different, but I've not figured out where that is configured, assuming >> it should be in the postgresql.conf file somewhere. It appears that the >> client_encoding is different as well, although I would have expected >> that to have been taken care when the databases were built. I have >> explicitly set the client_encoding in the postgresql.conf file, but >> haven't found where to set the database encoding. > > The database encoding can only be set at initdb time. Client_encoding is > only used to be able to convert from one encoding to another, assuming > that some conversion exists. You might be able to get it working by > setting the client encoding to something like iso-8859-1. Thanks to all for all the assistance with these issues. I am not successfully replicating and will be testing our 'replication_role' solution. I'll post an update as to our successes (as that is what I expect :) ) -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin
- Previous message: [Slony1-general] replication set up, but no replication
- Next message: [Slony1-general] table truncation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list