Aha, I get you Cédric

Thanks for the pointers.

Glyn

--- Cédric Villemain <cedric.villemain at dalibo.com> wrote:

> Glyn Astill a écrit :
> > Hi Cédric,
> >
> >
> > --- Cédric Villemain <cedric.villemain at dalibo.com> wrote:
> >
> >   
> >> I have just look at it a quick view ... you would use the common
> 
> >> postgresql command line options ....
> >>
> >>     
> >
> > You mean I should use the postgresql command line options? ?? I'm
> not
> > sure what you mean here
> >   
> 
> the command line options for psql. Like
> -U user -d dbname ....
> 
> >   
> >> Else, I suggest you to add a table to your set, like
> >> 'last_update_set_X' 
> >> then update it every 1 second for ex.
> >> And check the last update on all nodes, you will have a real
> mesure
> >> of 
> >> the effective lag.
> >>     
> >
> > Yes I agree with you, I will do this and I'll use the script that
> > comes with slony when I get around to it.
> >
> >   
> >> I prefer (or also) check replication outside system provided by
> the
> >>
> >> replication engine itself ....
> >>
> >>     
> >
> > Not sure what you mean?
> >   
> I mean that I prefer check that the replication is ok with the
> above table.
> I do also with sl_* but then you trust the info provided by the
> slony 
> himself.
> 
> It is like ask a banker to check himself if is paying taxes
> correctly  =)
> >
> >       __________________________________________________________
> > Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com
> >
> >
> >   
> 
> 
> -- 
> Cédric Villemain
> Administrateur de Base de Données
> Cel: +33 (0)6 74 15 56 53
> http://dalibo.com - http://dalibo.org
> 
> 



      __________________________________________________________
Sent from Yahoo! Mail - a smarter inbox http://uk.mail.yahoo.com