Thx for the fix.

I havn't test the last HEAD release yet. I 'm afraid i won' t have any time
for this by now.
The generated *.slonik files helps me as sample that i modify with my little
hands...

Btw, the store_paths.slonik file looks weird :

STORE PATH (SERVER=3D1, CLIENT=3D2, CONNINFO=3D'dbname=3Dmydb host=3Dmyhost1
user=3Dpgslony port=3D5432'); else
STORE PATH (SERVER=3D1, CLIENT=3D2, CONNINFO=3D'dbname=3Dmydb host=3Dmyhost2
user=3Dpgslony port=3D5432');
STORE PATH (SERVER=3D2, CLIENT=3D1, CONNINFO=3D'dbname=3Dmydb host=3Dmyhost2
user=3Dpgslony port=3D5432'); else
STORE PATH (SERVER=3D2, CLIENT=3D1, CONNINFO=3D'dbname=3Dmydb host=3Dmyhost2
user=3Dpgslony port=3D5432');

and i'm not really estonished by error produced :

$> slonik store_paths.slonik
store_paths.slonik:2: ERROR: syntax error at or near else

another bug or wrong use?


I go on on with with some idea of improvement even if i guess they are so
obvious that they might already be in your roadmap :
- why not separate files among thiner functionnality : 1 file *.slonik file
for creating cluster, another for nodes, another for set, another for
tables, another for sequences , ..., what else?, and subscription
- why not produces undo *.slonik files (with same granularity) : remove
subscription, ..., untill remove cluster (even i still not sure of my self
how to make so with bare metal).

With full respect due slony people work (I do know time is nerve war),

rgds


2008/3/5, Christopher Browne <cbbrowne at ca.afilias.info>:
>
> "St=E9phane A. Schildknecht" <stephane.schildknecht at postgresqlfr.org>
> writes:
> > lio bod a =E9crit :
> >> Hello world,
> >>
> >> Still having fun with supplied shell scripts :
> >>
> >> After setting env variales, i made work configure-replication.sh
> >>
> >>>/tmp/slonytest-temp.Q17311/create_set.slonik
> >>>/tmp/slonytest-temp.Q17311/create_set.slonik:29: ERROR: syntax error at
> >> or near snum
> >>
> >> The file create_set.slonik looks like that :
> >>
> >> [.../...]
> >> set add table (id=3D2, set id=3D1, origin=3D1, fully qualified
> >> name=3D'public.mytable1', comment=3D'mycluster table public.mytable1');
> >> set add sequence (id=3D1, set id=3D1, origin=3D1, fully qualified
> >> name=3D'public.mysequence1', comment=3D'mycluster sequence
> >> public.mysequence1'); snum=3D2
> >> [.../...]
> >>
> >> Where does the 'snum=3D2' comes from?
> >
> > It's a bug in the script. A carriage return has disappeared on line 150.
> >
> > You should have
> >
> > 150c150,151
> > <     echo "set add sequence (id=3D${snum}, set id=3D1, origin=3D1, ful=
ly
> qualified
> > name=3D'${seq}', comment=3D'${CLUSTER} sequence ${seq}');" >> $SETUPSET
> > snum=3D`expr ${snum} + 1`
> > ---
> >>     echo "set add sequence (id=3D${snum}, set id=3D1, origin=3D1, fully
> qualified
> > name=3D'${seq}', comment=3D'${CLUSTER} sequence ${seq}');" >> $SETUPSET
> >>     snum=3D`expr ${snum} + 1`
>
> Fixed in REL_1_2_STABLE; it's evidently fine in CVS HEAD...
> --
> select 'cbbrowne' || '@' || 'ca.afilias.info';
> <http://dba2.int.libertyrms.com/>
> Christopher Browne
> (416) 673-4124 (land)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20080306/=
d19a637d/attachment.htm