From: imad <immaad@gmail.com>
To: Dylan Lorimer <edylan@google.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Long SQL Update Question
Date: Sat, 4 Nov 2006 14:08:40 +0500
Message-ID: <1f30b80c0611040108n5235c135qe5fff990f1636e76@mail.gmail.com> (raw)
In-Reply-To: <3ddac38d0611031421s3c3f48ffoeea9a9bd1f86a71c@mail.gmail.com>
References: <3ddac38d0611031421s3c3f48ffoeea9a9bd1f86a71c@mail.gmail.com>
You can turn on logging ... but your transaction would be even slower
after that.
The following links should give you some pointers:
http://www.postgresql.org/docs/8.1/static/monitoring-stats.htmlhttp://www.postgresql.org/docs/8.1/static/monitoring.html
Also try Nagios monitoring plugins for PostgreSQL. Get it from pgFoundry.
--Imad
www.EnterpriseDB.com
On 11/4/06, Dylan Lorimer <edylan@google.com> wrote:
> So I kicked off a SQL transaction that has been running for 30+ minutes. Is
> there any way to monitor it to know if it has possibly hanged or not? To be
> fair, it is an update on 4+ million rows, so I expect it to run for a bit.
> But any stats or metrics I can get would be helpful.
> Cheers,
> dylan
>
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-sql@postgresql.org
Cc: immaad@gmail.com, edylan@google.com
Subject: Re: Long SQL Update Question
In-Reply-To: <1f30b80c0611040108n5235c135qe5fff990f1636e76@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