X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9D8CA53825 for ; Tue, 12 Apr 2005 07:47:22 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 34042-01 for ; Tue, 12 Apr 2005 10:46:51 +0000 (GMT) Received: from viper.eo.pl (viper.eo.pl [217.17.46.133]) by svr1.postgresql.org (Postfix) with ESMTP id 10DC353802 for ; Tue, 12 Apr 2005 07:46:49 -0300 (ADT) Received: from xxx.hq.eo.pl ([192.168.20.129] helo=localhost.localdomain) by viper with asmtp (TLS-1.0:RSA_AES_128_CBC_SHA:16) (Exim 4.34) id 1DLIup-0006ft-FF for pgsql-performance@postgresql.org; Tue, 12 Apr 2005 12:46:49 +0200 Received: from depesz by localhost.localdomain with local (Exim 4.50) id 1DLIup-00030C-2L for pgsql-performance@postgresql.org; Tue, 12 Apr 2005 12:46:43 +0200 Date: Tue, 12 Apr 2005 12:46:43 +0200 From: hubert lubaczewski To: pgsql-performance@postgresql.org Subject: profiling postgresql queries? Message-ID: <20050412104643.GB11445@eo.pl> Reply-To: hubert.lubaczewski@eo.pl Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline X-info-en-1: this message *may* reflect my personal opinion. it is *not* X-info-en-2: intended to reflect those of my employer, or anyone else. X-info-pl-1: wszelkie opinie =?iso-8859-2?Q?wyra=BFone_?= =?iso-8859-2?Q?w_tym_li=B6cie_prezentuj=B1_wy=B3=B1cznie_pogl=B1dy?= X-info-pl-2: autora listu. opinie =?iso-8859-2?Q?te_?= =?iso-8859-2?Q?w_=BFadnym__razie_nie__wyra=BFaj=B1__pogl=B1d=F3w?= X-info-pl-3: pracodawcy autora =?iso-8859-2?Q?listu_?= =?iso-8859-2?Q?_ani__innych__zwi=B1zanych__z__nim__os=F3b=2E?= User-Agent: Mutt/1.5.8i X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200504/223 X-Sequence-Number: 11620 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.