On Tue, Nov 24, 2009 at 3:59 PM, Jerry Champlin <jchamplin@xxxxxxxxxxxxxxxxxxxxxxxx> wrote: > You may want to consider using partitioning. That way you can drop the > appropriate partition and never have the overhead of a delete. Hum, I don't think it's doable in my case; the partitioning is not know a priori. First t1 is fully populated, then the data is loaded and manipulated by my application, the result is stored in t2; only then I want to remove (part of) the data from t1. thanks, Luca -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
