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=1, CLIENT=2, CONNINFO='dbname=mydb host=myhost1
user=pgslony port=5432'); else
STORE PATH (SERVER=1, CLIENT=2, CONNINFO='dbname=mydb host=myhost2
user=pgslony port=5432');
STORE PATH (SERVER=2, CLIENT=1, CONNINFO='dbname=mydb host=myhost2
user=pgslony port=5432'); else
STORE PATH (SERVER=2, CLIENT=1, CONNINFO='dbname=mydb host=myhost2
user=pgslony port=5432');
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 <[EMAIL PROTECTED]>:
>
> "Stéphane A. Schildknecht" <[EMAIL PROTECTED]>
> writes:
> > lio bod a écrit :
> >> 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=2, set id=1, origin=1, fully qualified
> >> name='public.mytable1', comment='mycluster table public.mytable1');
> >> set add sequence (id=1, set id=1, origin=1, fully qualified
> >> name='public.mysequence1', comment='mycluster sequence
> >> public.mysequence1'); snum=2
> >> [.../...]
> >>
> >> Where does the 'snum=2' 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=${snum}, set id=1, origin=1, fully
> qualified
> > name='${seq}', comment='${CLUSTER} sequence ${seq}');" >> $SETUPSET
> > snum=`expr ${snum} + 1`
> > ---
> >> echo "set add sequence (id=${snum}, set id=1, origin=1, fully
> qualified
> > name='${seq}', comment='${CLUSTER} sequence ${seq}');" >> $SETUPSET
> >> snum=`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)
>
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
