| From: | hubert lubaczewski <hubert(dot)lubaczewski(at)eo(dot)pl> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | profiling postgresql queries? |
| Date: | 2005-04-12 10:46:43 |
| Message-ID: | 20050412104643.GB11445@eo.pl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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
queries.
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 time: 1 secons
trigger a: 0.50 second
trigger b: 0.25 second
index update: 0.1 second
something like this.
is it possible?
will it be ever possible?
hubert
--
hubert lubaczewski
Network Operations Center
eo Networks Sp. z o.o.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Held | 2005-04-12 13:41:55 | Re: 4 way JOIN using aliases |
| Previous Message | Keith Worthington | 2005-04-12 00:43:46 | Re: 4 way JOIN using aliases |