I think I'm missing something obvious here...

I've got Slony running in my test evironment with a simple 2-node setup.

I want to upgrade Postgres on a slave node from Pg 8.2 to 8.3 Beta
with a minimal amount of downtime. So the idea is that I bring up
another Pg instance on a different port and add the node to the
cluster.

So I have 3 nodes with both Slaves on the same machine:
Node 1 - "Master" node
Node 2 - "Slave" node Pg 8.2
Node 3 - "Slave" node Pg 8.3

Now that I've verified that the new Pg instance is working properly, I
want to take down the Pg 8.2 bring up the Pg 8.3 on the standard Pg
port. That in itself is easy enough to do:

1. Stop all slon daemons.
2. Drop Pg 8.2 node from cluster.
3. Stop Pg 8.2
4. Restart Pg 8.3 on the old port
5. Update slon config for old port.
6. Update sl_path info how???
7. Restart slon daemons

Step 6 is where I get a bit unsure/lost. It looks like there is
connection information stored in the sl_path table and that should be
updated before starting up the slon daemons.

The question is: what's the best way to do it? Manually? Or will the
slon daemons magically figure this out on their own?

-Dave