Thank you all for your help. I've already loaded a dump our postgres 8.1 database into a dev server running 9.0 and verified that our applications work as expected. I was just mainly concerned that slony wouldn't fully support that big of a jump in versions. I thought I was going to have to use slony 1.2 to migrate from postgres 8.1 to 8.3, then upgrade to slony 2.0, then make the final jump from postgres 8.3 to 9.0. I'm relieved that I won't have to go through all that hassle. Thank you very much for adding support for postgres 9.0 in slony 1.2!

-Sam Choukri


On Apr 26, 2011, at 8:38 AM, Christopher Browne wrote:

> On Mon, Apr 25, 2011 at 8:11 PM, Sam Choukri <sam at eventful.com> wrote:
>> Hello,
>> 
>> I am maintaining a pair of database servers on CentOS 5 running Posgtres 8.1.18 and Slony 1.2.22 (1 master to 1 slave). I would like to upgrade the database to Postgres 9.0, but I do not have the option of doing a standard drop and restore. Therefore, I'd like to use Slony to replicate from 8.1 to 9.0, then do a switchover.
>> 
>> The release notes for Slony 1.2.22 says it added explicit support for Postgres 9.0 so I'm cautiously optimistic I can do it. But is it a good idea? Any gotchas I should be concerned about?
> 
> Your "gotchas" will generally have to do with changes in Postgres features.
> 
> Notably, somewhere between 8.1 and 9.0, Postgres got quite a bit more
> strict about its handling of UTF-8, and a lot of people had headaches
> out of complaints of "invalid encoding".
> 
> The issue got discussed pretty thoroughly here:
> <http://lists.slony.info/pipermail/slony1-general/2010-April/010596.html>
> 
>> By the way, I could not find a search interface for the slony mail list archives. Does one exist?
> 
> We didn't put one in place; you can probably use search engines (e.g.
> - such as G**gl*)...
>