Mark Hagger wrote:
> On Tue, 2009-04-21 at 11:01 -0400, cbbrowne wrote:
>> I'm surprised you got far enough to be able to consider a MOVE SET request.
>>     
>
> In these cases I'd used the pgadmin slony admin interface to create 
> and configure these clusters, I guess that whatever that does
> is able to handle the hyphens ok.  However, the pgadmin stuff doesn't 
> allow more useful things like moves and failovers to be
> controlled so I backed up to using slonik commands directly and then 
> it all fell apart.
Ah, that's useful to know!

Slonik's parsing is evidently enforcing this, but the underlying 
functions aren't.

Consistency would suggest either:
a) Changing slonik to make it support the "richer" set of names, or
b) Changing functions that manipulate cluster names to complain if the 
cluster name isn't supposed to be valid...
> Incidently the documention for cluster names, eg at 
> http://www.slony.info/documentation/clustername.html, 
> <http://www.slony.info/documentation/clustername.html> has no mention of
> any potential restrictions on characters, or did I miss something 
> somewhere?
This issue hadn't been noticed before now.
>> The cluster name is handled by Slonik as an alphanumeric string, in much 
>> the same form as a SQL identifier, and it does not support quoting.
>>
>> It's conceivable that you might try running, on each node:
>>
>>   alter schema "_GB-LDC" rename to "_GB_LDC";
>>
>> I'd suggest trying that out in a test environment first :-)
>>     
>
> Thanks, I ended up dropping the cluster's and recreating them in a 
> "controlled way", by luck none of the effected databases were high 
> traffic or
> had large volumes of data.
>
> Regards,
>
I'm glad that worked out!  I'll see about getting this documented and/or 
validated.

-- 
output = ("cbbrowne" "@" "ca.afilias.info")
<http://dba2.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)
"Bother,"  said Pooh,  "Eeyore, ready  two photon  torpedoes  and lock
phasers on the Heffalump, Piglet, meet me in transporter room three"