From: Chris Hoover <revoohc@gmail.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: What happens on a commit?
Date: Tue, 22 May 2007 13:25:01 -0400
Message-ID: <1d219a6f0705221025i1c1d036eq4769b133cac7499@mail.gmail.com> (raw)
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: revoohc@gmail.com
Subject: Re: What happens on a commit?
In-Reply-To: <1d219a6f0705221025i1c1d036eq4769b133cac7499@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox