Hi,

We're hitting 400 requests per second and noticed that sl_log_? are 
growing a lot. This is also due to the fact that our tables have a lot 
of columns (more that 100). We noticed that slony stores each column and 
its value for each request in sl_log_x. Would it not be more optimized 
to store just the user request ? Actually, a user is just updating a few 
column, or inserting a tuple by giving some attributes but not all, 
however as slony stores every column with its value it sl_log_x, these 
tables are growing very fast :-(

Another question :

How logswitch is used in slony ? I try a logswitch.start() and I had to 
move date between sl_log_1 and sl_log_2 to finish it. How does it work ? 
which thread is using this function ?

Regards.

-- 
Cyril SCETBON