On L, 2005-03-12 at 14:05 -0800, Josh Berkus wrote: > Tambet, > > > In one of our applications we have a database function, which > > recalculates COGS (cost of good sold) for certain period. This involves > > deleting bunch of rows from one table, inserting them again in correct > > order and updating them one-by-one (sometimes one row twice) to reflect > > current state. The problem is, that this generates an enormous amount of > > tuples in that table. > > Sounds like you have an application design problem ... how about re-writing > your function so it's a little more sensible?
Also, you could at least use a temp table for intermediate steps. This will at least save WAL traffic. -- Hannu Krosing <[EMAIL PROTECTED]> ---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
