"Mindaugas Riauba" <[EMAIL PROTECTED]> writes:
>> Well, try it without the trigger. If performance improves markedly, it
>> might be worth rewriting in C.

>   Nope. Execution time is practically the same without trigger.

>> If not, you're probably saturating the disk I/O -

>   Bottleneck in this case is CPU. postmaster process uses almost 100% of
> CPU.

That seems very odd.  Updates should be I/O intensive, not CPU
intensive.  I wouldn't have been surprised to hear of a plpgsql trigger
consuming lots of CPU, but without it, I'm not sure where the time is
going.  Can you show us an EXPLAIN ANALYZE result for a typical update

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Reply via email to