In response to salman <salmanb at quietcaresystems.com>:
> 
> I looked through the docs already but I have a couple of questions about 
> the process and wanted clarification.
> 
> I would like to use the slony recommended method to upgrade our 8.2.x pg 
> install to 8.3.1. If I understand the documentation correctly, I need to 
> install 8.3.1 on the server, make a slave node to the master and let 
> slony sync the data between the two. Then, once the data is fairly 
> in-sync, stop write applications, and issue a move set command to start 
> using the new, updated master.
> 
> The questions I have are as follows:
> 
> 1) Since node IDs x,y are already in use by the primary master (x) and 
> slave (y), the new 8.3.1 node will receive an ID of 'z' (1,2,3 in 
> numbers). Is it possible to rename the new node (z) to x?  I was unable 
> to find any docs about this.

I don't know the answer to this one.

> 2) Am I correct to assume that any subscriber nodes will also receive 
> the move set notification and start receiving notifications from the new 
> master? Or would this require any reconfig on the slave node? I was 
> unable to find any docs related to this, also.

Here you are correct.  Slony will reshape the cluster when you do the
move set, and all nodes will adjust their subscriptions as needed, although
it's not always in the way you suspect.

Keep in mind that you can see what was done by looking at the
$cluster_name$.sl_subscribe table, and if anything isn't how you want
it, you can re-issue subscribe set() commands to reshape it manually
after the move set() has been done.

-- 
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/

wmoran at collaborativefusion.com
Phone: 412-422-3463x4023

****************************************************************
IMPORTANT: This message contains confidential information and is
intended only for the individual named. If the reader of this
message is not an intended recipient (or the individual
responsible for the delivery of this message to an intended
recipient), please be advised that any re-use, dissemination,
distribution or copying of this message is prohibited. Please
notify the sender immediately by e-mail if you have received
this e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or
error-free as information could be intercepted, corrupted, lost,
destroyed, arrive late or incomplete, or contain viruses. The
sender therefore does not accept liability for any errors or
omissions in the contents of this message, which arise as a
result of e-mail transmission.
****************************************************************