Re: performance with triggers depends on table size? - Mailing list pgsql-general

From Christian Mock
Subject Re: performance with triggers depends on table size?
Date
Msg-id 20020816104841.GB29665@notemock.coretec.at
Whole thread Raw
In response to Re: performance with triggers depends on table size?  (Manfred Koizar <mkoi-pg@aon.at>)
List 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

pgsql-general by date:

Previous
From: Adrian 'Dagurashibanipal' von Bidder
Date:
Subject: Re: Why choose PostreSQL and not MySQL or Oracle!!
Next
From: Justin Clift
Date:
Subject: Finally, a list of *big* companies using PostgreSQL for *serious* projects. Why use PostgreSQL? Here's why.