>why slony (>= 1.2.17) is not creating (when possible) a TRUNCATE
>trigger
 to manage that situation? or there is another technique you
>are 
using?


In section 1.5 Current Limitations of the slony documentation, it specifically states that slony cannot generate a truncate trigger. So for replicated tables, it is either best to use a DELETE statement (can take a long time) or manually truncate the specific table in the master and slave. One workaround would be to use a SLONIK EXECUTE SCRIPT to propagate the TRUNCATE to all slaves.

Melvin Davidson 
  




      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20100402/661a8a1e/attachment.htm