On Tue, 20 Nov 2007, Christopher Browne wrote:

> No, there is no notion of modifying the node ID; the ID is very deeply 
> intertwined into replication state across all the nodes, with the result that 
> trying to alter the ID would be likely to lead to potential for *enormous* 
> confusion within the replication system.
>
> There is no reason to have a "node 1" around; many of the tests assume its 
> absence, and in most of our production clusters, we use node numbers that are 
> *somewhat* meaningful.
>
> For instance, several clusters consist of nodes:
> 8141
> 8142
> 8143
> 8194
>
> Where:
>
> - "81" indicates that it's a PostgreSQL 8.1 instance  (we may soon have nodes 
> starting with "83")
> - 4 versus 9 indicates which data centre the node is at
> - below all of that, we have a more-or-less serial value, 1,2,3,4
>
> It's not quite wonderful, but it's mnemonic enough to be useful...

The only reason I consider changing it, is that the event node defaults to 1. 
Is it possible to define what the default event node without changing the code 
and recompiling?

  EVENT NODE = ival
     (Optional) The ID of the current origin of the set. Default value is 1.

It just means we have to remember to specify it in the slonik scripts after 
the upgrade.

-- 
Jeff Frost, Owner 	<jeff at frostconsultingllc.com>
Frost Consulting, LLC 	http://www.frostconsultingllc.com/
Phone: 650-780-7908	FAX: 650-649-1954