| From: | Christian Mock <cm(at)coretec(dot)at> |
|---|---|
| To: | Manfred Koizar <mkoi-pg(at)aon(dot)at> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: performance with triggers depends on table size? |
| Date: | 2002-08-16 10:48:41 |
| Message-ID: | 20020816104841.GB29665@notemock.coretec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Aug 16, 2002 at 11:19:18AM +0200, Manfred Koizar wrote:
> do you *need* to update event_stats in a trigger? What I mean is, if
Well, of course I don't need to, but given that that table is not only
inserted into, but also updated, I'd rather have the stats kept in sync
by the trigger than in the application -- if not, I could use mysql.
I did a big import (3.7 mio rows) and it worked out pretty well with
the regular vacuum -- 50 rows/sec on average, and no more sawtooth
pattern.
Regards,
cm.
--
Christian Mock Wiedner Hauptstrasse 15
Senior Security Engineer 1040 Wien
CoreTEC IT Security Solutions GmbH +43-1-5037273
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Moritz Sinn | 2002-08-16 12:24:06 | Re: writing own cast |
| Previous Message | Adrian 'Dagurashibanipal' von Bidder | 2002-08-16 10:14:59 | Re: Why choose PostreSQL and not MySQL or Oracle!! |