Hi Salman,

I just did this whole exercise with 1 master and 3 slaves and some of 
the main points:

    * need two postgres installations running at the same time on
      different ports 8.2.3, 8.3.1)
    * I guess you will upgrade slony to 1.2.14 as well, as Christopher
      pointed out need to do the "configure" and "make install" but if
      you are upgrading your 8.2.3 slony installation as well, make sure
      that you run "make clean" before doing the make install. else you
      will get older lib files and you will get that error below (i got
      it too)
    * using MOVE_SET only switch the subscription of the nodes in
      question, not other nodes that subscribe the original master,
      those need to be switched manually with "Subscribe_set"
    * If you like me, want to drop the 8.2.3 node and change the port of
      the 8.3.1 to the old port of the 8.2.3. Take the dbs down change
      the port in postgres.conf take the 8.3.1 db up on the new port
      then for each node you need to issue the "store path" command to
      upgrade the paths so all nodes know the correct new port.

You can check my previous messages on this list as i went through most 
of the problems you are likely to face doing this.


Salman wrote:
> All,
>
> I am trying to upgrade our current version of postgres 8.2.3 to 8.3.1.
> I have installed 8.3.1 on the same machine as our 8.2.3 install and am
> now trying to add the new install as a slave. When I run the slonik
> commands, I get an error back saying that $libdir/xxid.so was not
> found.
>
> I did check in the 8.2.3 and 8.3.1 $libdir-s and while there is a
> xxid.so file in the 8.2.3 $libdir, there isn't one in the 8.3.1; the
> config options for both installs were kept the same.
>
> I tried a google search already but could not find a work around for
> the issue. http://linuxfinances.info/info/faq.html#AEN47452 recommends
> only having one install of postgres, but that's not possible during an
> upgrade.
>
> Would just copying the lib file from one install to another work? I
> assume that's likely to break things.
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
>