>> 5. Finally, I'll drop the indexes on the parent table and >> truncate it. Luckily I noticed the problem with TRUNCATE and partitioning before my work got to production. TRUNCATE cascades automatically and silently to child tables, which was not my intent. This is mentioned here: http://wiki.postgresql.org/wiki/Table_partitioning But is not mentioned in the official documentation for TRUNCATE: http://www.postgresql.org/docs/9.0/static/sql-truncate.html The work-around we used was to put the TRUNCATE statement ahead of the ALTER TABLE .. INHERIT statements in our final transaction. Mark -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
