| From: | Alex Turner <armtuk(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | hubert(dot)lubaczewski(at)eo(dot)pl, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: profiling postgresql queries? |
| Date: | 2005-04-12 14:18:31 |
| Message-ID: | 33c6269f05041207182473d08b@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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.
Is the best thing just to write triggers in C (I really don't want to
put this stuff in the application logic because it really doesn't
belong there).
Alex Turner
netEconomist
On Apr 12, 2005 10:10 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> hubert lubaczewski <hubert(dot)lubaczewski(at)eo(dot)pl> 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 desperate
> you could load up a play server with your data and test.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-04-12 14:35:40 | Re: Slow update |
| Previous Message | Bendik R.Johansen | 2005-04-12 14:12:32 | Slow update |