John Papandriopoulos <dr.jpap@xxxxxxxxx> writes: > I've recreated the same example with just one parent table, and 4096 child tables. > SELECT query planning is lightning fast as before; DELETE and UPDATE cause my machine to swap. > What's different about DELETE and UPDATE here? Hmm. Rules? Triggers? You seem to be assuming the problem is at the planner stage but I'm not sure you've proven that. regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
