The slave is behind because when i modify or insert a record in the master
database,
 I do the same query on both database, and it appears in the slave several
minutes after.


======================================================================================================
The following command has been run on  March 11th on the slave
The master ( 136.100.100.247 ) seems to wait for a reply from the slave

[root at webapp-2 root]# ps -auxww | grep slon

slony    16455  0.0  0.1 61548 1748 ?        S    Mar10   0:00
/usr/local/slony/src/slon/slon -d 4 -s 10000 -g 10 replication dbname=lims
postgres 16460  0.5  0.3 10312 3496 ?        S    Mar10   5:50 postgres:
slony lims [local] async_notify waiting
postgres 16468  0.5  0.3 10572 3740 ?        S    Mar10   5:52 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 16471  0.3  0.3 11244 4120 ?        S    Mar10   3:24 postgres:
slony lims [local] INSERT waiting
postgres 16473  0.1  0.4 11168 4184 ?        S    Mar10   2:09 postgres:
slony lims [local] SELECT waiting
postgres 16475  0.2  0.3 10452 3704 ?        S    Mar10   2:52 postgres:
slony lims [local] COMMIT waiting
postgres 16736  0.5  0.3 10572 3748 ?        S    Mar10   5:29 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 16773  0.4  0.3 10572 3788 ?        S    Mar10   5:11 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 16791  0.4  0.3 10572 3784 ?        S    Mar10   4:57 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 17194  0.4  0.3 10572 3716 ?        S    Mar10   4:34 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 17302  0.4  0.3 10572 3768 ?        S    Mar10   4:21 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 17502  0.4  0.3 10572 3792 ?        S    Mar10   4:04 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 17516  0.4  0.3 10572 3796 ?        S    Mar10   3:54 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 17533  0.3  0.3 10508 3692 ?        S    Mar10   3:40 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 17538  0.3  0.3 10572 3796 ?        S    Mar10   3:33 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 17546  0.3  0.3 10572 3792 ?        S    Mar10   3:25 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 17562  0.3  0.3 10572 3792 ?        S    Mar10   3:16 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 17569  0.3  0.3 10572 3796 ?        S    Mar10   3:07 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 17588  0.3  0.3 10572 3788 ?        S    Mar10   2:52 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 17595  0.3  0.3 10572 3792 ?        S    Mar10   2:47 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 17614  0.3  0.3 10572 3788 ?        R    Mar10   2:37 postgres:
slony lims 136.100.100.247 async_notify
postgres 17624  0.3  0.3 10572 3788 ?        S    Mar10   2:26 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 17642  0.3  0.3 10576 3784 ?        S    Mar10   2:17 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 17667  0.3  0.3 10576 3764 ?        S    Mar10   2:04 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 17689  0.3  0.3 10576 3756 ?        S    Mar10   1:54 postgres:
slony lims 136.100.100.247 async_notify waiting
postgres 17715  0.3  0.2 10236 2904 ?        S    Mar10   1:42 postgres:
slony lims 136.100.100.247 async_notify waiting

===========================================================================================
select * from _replication.sl_status ;

st_origin|st_received|st_last_event|st_last_event_ts
|st_last_received|st_last_received_ts
1        |2          |249338       |2005-03-11 07:42:32.0538|248698
|2005-03-10 22:50:34.550142

|st_last_received_event_ts |st_lag_num_events|st_lag_time
|2005-03-10 22:05:36.564812|640              |09:37:26.577141


===========================================================================================
vacuum analyze verbose _replication.sl_log_1;

INFO:  --Relation _replication.sl_log_1--
INFO:  Pages 92: Changed 2, Empty 0; Tup 3566: Vac 0, Keep 0, UnUsed 15.
      Total CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO:  --Relation pg_toast.pg_toast_2530505--
INFO:  Pages 0: Changed 0, Empty 0; Tup 0: Vac 0, Keep 0, UnUsed 0.
      Total CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO:  Analyzing _replication.sl_log_1

Total query runtime: 218 ms.

===========================================================================================
vacuum analyze verbose _replication.sl_seqlog;

INFO:  --Relation _replication.sl_seqlog--
INFO:  Pages 32: Changed 1, Empty 0; Tup 4536: Vac 0, Keep 0, UnUsed 0.
      Total CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO:  Analyzing _replication.sl_seqlog

Total query runtime: 31 ms.

===========================================================================================
vacuum analyze verbose pg_listener;

INFO:  --Relation pg_catalog.pg_listener--
INFO:  Removed 20 tuples in 2 pages.
      CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO:  Pages 3: Changed 0, Empty 0; Tup 7: Vac 20, Keep 0, UnUsed 182.
      Total CPU 0.00s/0.00u sec elapsed 0.00 sec.
INFO:  Analyzing pg_catalog.pg_listener

Total query runtime: 32 ms.


-------------- next part --------------


***********************************************************************
NOTICE: This e-mail transmission, and any documents, files or previous
e-mail messages attached to it, may contain confidential or privileged
information. If you are not the intended recipient, or a person
responsible for delivering it to the intended recipient, you are
hereby notified that any disclosure, copying, distribution or use of
any of the information contained in or attached to this message is
STRICTLY PROHIBITED. If you have received this transmission in error,
please immediately notify the sender and delete the e-mail and attached
documents. Thank you.
***********************************************************************