> if the problem is caused by the the acquire lock->modify column->release
> lock on the table 1, then why does it increase significantly increase as the
> number of entries in the table 3 grows? The simulation maintains pretty much
> constant rate of new requests coming to table 3.
Are you vacuuming table 1 on a regular basis while you do this?
Accumulation of dead tuple versions in table 1 is a pretty severe
performance risk in the sort of scenario you are describing.
(I'm not sure why it would manifest as transactions showing "INSERT
waiting" state though.)
regards, tom lane
In response to
pgsql-sql by date
|Next:||From: Tomas Vondra||Date: 2006-01-07 16:03:35|
|Subject: how to transform list to table and evaluate an expression on it?|
|Previous:||From: Tom Lane||Date: 2006-01-06 20:52:08|
|Subject: Re: INSERT waiting under heavy load |