On Tuesday 20 November 2007 12:07:21 Jeff Frost wrote:
> 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?

well if you use altperl, you can just define the default node in the conf 
file...

>
>   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.



-- 
Darcy Buskermolen
Command Prompt, Inc.
+1.503.667.4564 X 102
http://www.commandprompt.com/
PostgreSQL solutions since 1997