On 10/18/2004 10:56 AM, Jan Wieck wrote:

> On 10/17/2004 6:46 PM, hannu at skype.net wrote:
> 
>> "Jan Wieck" <JanWieck at Yahoo.com> wrote:
>> 
>>>>
>>>> I am also unable to set subscription on slave (node 1) to forward=no
>>>> using
>>>> slonik command :
>>>> subscribe set ( id = 1, provider = 2, receiver = 1, forward = no);
>>>
>>> This problem was fixed in release 1.0.2 ... do you mind upgrading?
>> 
>> Now that I thought about it, I may be even running a *beta* version of
>> slon on the machine that services the slave. (Due to network structure it
>> is not on one of the database machines)
>> 
>> This may also cause some of the other problems I have described ;(
>> 
>> What do you think of an idea to make slon write its version number to log
>> and slonik to report it, perhaps on a -v switch.
> 
> You won't be able to do that in 1.0.3 any more. Slon will just refuse to 
> work with a database that does not have the 1.0.3 version of stored 
> procedures loaded or where the shared object for the C functions isn't 
> the 1.0.3 release one.
> 
>> 
>> My current quess that I may be running a beta version is based mainly on
>> the file date of binary (Jul 3) and some vague recollections of when I
>> asked the admin to install what to where - and i *think* that he upgraded
>> slon only on these machines which run postgres ;)
> 
> The only think that doesn't yet spit out its version number is slonik. 
> Some extra "echo version" shouldn't be too hard.

I have added a -v commandline switch to slon and slonik. It causes both 
to just report their version number and exit. Will be in 1.0.3.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #