> 
> Hmm.  Which file(s) were growing, exactly?  How many row updates is this
> run covering?
> 

The toast table gets about 90 percent of the growth, followed by the toast 
index at about 9 percent. The actual table + primary key stay at about 2M each.

I neglected to mention what the update statement actually was :

UPDATE grow SET body = ? WHERE id = ?

So the untoasted elements are not being altered at all...

A typical run has 2 threads each of which updates the entire table (20,000 
rows) every 2000 s.

The vacuum thread manages to get 6-7 vacuums in before both threads update the 
entire table.

regards

Mark



Mon, 20 May 2002 21:37:17 GMT
<markir@slingshot.co.nz>
Re: Unbounded (Possibly) Database Size Increase - Toasting 