Mon Dec 17 08:13:33 PST 2007
- Previous message: [Slony1-general] Different indexes on slave
- Next message: [Slony1-general] will truncate mess up slony?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I'm about to split a big table of mine using partitions. I've done some testing on a test database, and the part of actually moving the data from the current table to each partition will take about 5 days, broken up into small bits of work as transactions. Once the data is moved, I am left with a HUGE table which is otherwise empty. A test run of "vacuum full" on the table takes nearly 2 hours. I can't really afford that on the production system, obviously. So my question is, how to use TRUNCATE on that table? Since it is already empty, does it matter to slony if I just issue TRUNCATE on each of the nodes? Or do I need to go through the execute script slonik command? Also, is TRUNCATE in this manner safe at all for slony? Thanks!
- Previous message: [Slony1-general] Different indexes on slave
- Next message: [Slony1-general] will truncate mess up slony?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list