Le 03/04/2010 03:50, Melvin Davidson a écrit :
>> 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.
> 

Well, the limitation was understandable when PostgreSQL didn't have
TRUNCATE trigger. Now that it has (8.4 new capacity), it should probably
get added to Slony.


-- 
Guillaume.
 http://www.postgresqlfr.org
 http://dalibo.com