hi
i'm not totally sure i should ask on this mailing list - so if you think
i should better ask someplace else, please let me know.
the problem i have is that specific queries (inserts and updates) take a
long time to run.
of course i do vacuum analyze frequently. i also use explain analyze on
hubert lubaczewski [EMAIL PROTECTED] writes:
and it made me wonder - is there a way to tell how much time of backend
was spent on triggers, index updates and so on?
In CVS tip, EXPLAIN ANALYZE will break out the time spent in each
trigger. This is not in any released version, but if you're
On Tue, Apr 12, 2005 at 10:18:31AM -0400, Alex Turner wrote:
Speaking of triggers...
Is there any plan to speed up plpgsql tiggers? Fairly simple
crosstable insert triggers seem to slow my inserts to a crawl.
plpgsql is quite fast actually. if some triggers slow inserts too much,
i guess you
On Tue, Apr 12, 2005 at 12:46:43PM +0200, hubert lubaczewski wrote:
the problem is that both the inserts and updated operate on
heavy-tirggered tables.
and it made me wonder - is there a way to tell how much time of backend
was spent on triggers, index updates and so on?
like:
total query
On Tue, Apr 12, 2005 at 08:43:59AM -0600, Michael Fuhr wrote:
8.1devel changes frequently (sometimes requiring initdb) and isn't
suitable for production, but if the trigger statistics would be
helpful then you could set up a test server and load a copy of your
database into it. Just beware
