Why is the number of dead tuples causing the performance of deferred triggers to degrading so rapidly (exponentionally)?

From: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
To: pgsql-performance(at)postgresql(dot)org
Subject: Why is the number of dead tuples causing the performance of deferred triggers to degrading so rapidly (exponentionally)?
Date: 2004-08-17 21:33:42
Message-ID: 200408172333.42561.ftm.van.vugt@foxi.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Obviously,

this part of tr_f_def():

******************************
-- delete the contents
-- delete from f;
IF EXISTS (SELECT 1 FROM f) THEN
DELETE FROM F;
VACUUM F;
END IF;
******************************

should simply read:

******************************
-- delete the contents
delete from f;
******************************

--
Best,

Frank.

Browse pgsql-performance by date

  From Date Subject
Next Message Josh Berkus 2004-08-17 23:03:43 Re: Why is the number of dead tuples causing the performance of deferred triggers to degrading so rapidly (exponentionally)?
Previous Message Frank van Vugt 2004-08-17 21:29:52 Why is the number of dead tuples causing the performance of deferred triggers to degrading so rapidly (exponentionally)?