> Hi,
>
> In the coming days, I think we'll be required to change the name of a
> database that has most of its tables replicated with slony to a number
> of nodes.
>
> Does anyone know off-hand if this will this break slony (1.1.5) and if
> I can somehow change the name and get away with not removing slony and
> reinstalling it on my databases?

You should be able to stay quite short of "removing & installing."

There are two places where configuration needs to be changed:

1.  Invocation of the slon for that node; it'll need to point to the new
location...

2.  Paths in sl_path that point to the old location need to change to the
new...

This would involve a slonik script with one STORE PATH for each entry that
used to reference the old location.

I think you want to take the slons down for a minute on this (probably not
a problem in that DBs are going down)...

The sequence I'd expect to work:

- Stop all slons

- Rename the database

- Submit the slonik script with revised paths

- Restart all slons, notably with the config changed for the renamed
database.

You *might* need to do a second restart of slons in order for all the
nodes to recognize the new location.

What's most probable is that the renaming leads to what amounts to a brief
outage when some slons can't get at the renamed node.  As long as that DSN
doesn't match match a "former" DSN for some other node (e.g. - you swapped
node 1 with node 5), there's not even a chance of confusion.

Since each connect includes a query to check that the node number matches
expectations, even if you did a swap, those node number checks should
protect you against anything really bad happening...