Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 810259FBB27 for ; Tue, 22 May 2007 14:25:17 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 12897-04-2 for ; Tue, 22 May 2007 14:25:05 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by postgresql.org (Postfix) with ESMTP id 66B229FBB17 for ; Tue, 22 May 2007 14:25:06 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id k3so263067ugf for ; Tue, 22 May 2007 10:25:02 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=PslkylaqvIPAgyXcsn+GhUXvwbjs1OOyJAvemopsCGUX8Ecj83GusX/08gAVB/2yZ5Nip3ScFLEOgfC5uBw+vdjHjWJqJnjt95KtHntMDhlbvOW65hYIuBtOEelki9jsKqQNjnaXaMVya/tfrCgMNoonLVHo7+vl7FijMez1pxw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=CekkxF23YLbYp9xfXnkGiiKCTdMJtvsug4BmDR+EKaycW8Jjxi9jy2kudqgDua986+33+aQOUdV6O9WB6aN6GiBlP8cfR8WDxDDSBYZpATNL7FGsl/rCtZfKKmxyBxcDwOvjq1xLb361bp/LF2mbMpUAXy/n6gEAYpT3FZGIOaI= Received: by 10.78.130.6 with SMTP id c6mr1518407hud.1179854701857; Tue, 22 May 2007 10:25:01 -0700 (PDT) Received: by 10.78.201.16 with HTTP; Tue, 22 May 2007 10:25:01 -0700 (PDT) Message-ID: <1d219a6f0705221025i1c1d036eq4769b133cac7499@mail.gmail.com> Date: Tue, 22 May 2007 13:25:01 -0400 From: "Chris Hoover" To: "pgsql-admin@postgresql.org" Subject: What happens on a commit? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_76677_11204587.1179854701824" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/223 X-Sequence-Number: 25543 ------=_Part_76677_11204587.1179854701824 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I am trying to diagnose a slowness issue in some of my databases. I think the issue is due to a hardware/network upgrade over the weekend, but like all dba's, I have to prove it. Right now, I have almost all commits being issues taking between 1 and 5 seconds to complete. The can take as long as 20 seconds. What exactly happens when a commit is issues to PostgreSQL? Is there a way to trace what is going on internally? I do have a large process that I can start that will run many transactions during a single session. Anyway, any help would be appreciated. Thanks, Chris PG 8.1.3 RH 4.0 AS ------=_Part_76677_11204587.1179854701824 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I am trying to diagnose a slowness issue in some of my databases.  I think the issue is due to a hardware/network upgrade over the weekend, but like all dba's, I have to prove it.

Right now, I have almost all commits being issues taking between 1 and 5 seconds to complete.  The can take as long as 20 seconds.  What exactly happens when a commit is issues to PostgreSQL?

Is there a way to trace what is going on internally?  I do have a large process that I can start that will run many transactions during a single session.

Anyway, any help would be appreciated.

Thanks,

Chris

PG 8.1.3
RH 4.0 AS
------=_Part_76677_11204587.1179854701824--