On Wed, 14 Feb 2007 12:02:23 -0800, Darcy Buskermolen <[EMAIL PROTECTED]> wrote:
>>
>> 1) I think the whole wrap-slonik-with-perl approach is generally wrong
>> -- what I would really like to see is that slonik itself would be
>> modified so that it became more interactive client, like psql. Now I
>> don't know anything about how slonik works, and I don't even know if my
>> suggestion is feasible, but I think it would be the most simple and
>> effective way to control slony. For example, you could have slonc -d
>> <clustername> and then execute any commands necessary (I agree with Mark
>> Stosberg with the naming issue, slonc is better than slonik). Also slonc
>> could have -f switch for files etc.
>
> slonik is for the most part a wrapper to the plpgsql functions within the
> database, so the idea of making slonc an interactive client is not as far
> fetched as you may first think.
>
But this is a disadvantage as well:
slonik's dialect isn't very user-friendly regarding to an interactive language,
you have to play with cluster id's, table id's and node id's and this makes it
a little bit "rough"....btw. this bothers me in the altperl scripts as well.
An interactive slonik could to be extended to deal with identifiers, so people
could easily create clusters with "descriptive" parameters and they don't have
to play
around with anonymous numbers...
Hmm, what about an interactive slonc with altperl, much like cyradm maybe?
Bernd
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
