From: Carlo Stonebanks <stonec.register@sympatico.ca>
To: pgsql-performance@postgresql.org
Subject: Re: commit so slow program looks frozen
Date: Thu, 26 Oct 2006 13:49:57 -0400
Message-ID: <ehqsev$18pc$1@news.hub.org> (raw)
References: <6E0907A94904D94B99D7F387E08C4F570192F2D0@FALCON.INSIGHT>
<ehqhpe$20jt$1@news.hub.org>
<b42b73150610260806le117c55s126585ca6421cb0f@mail.gmail.com>
> when it happens, make sure to query pg_locks and see what is going on
> there lock issues are not supposed to manifest on a commit, which
> releases locks, but you never know.
There aren't any pedning locks (assuming that pgAdmin is using pg_locks to
display pendin glocks).
> There have been reports of
> insonsistent lock ups on windows (espeically multi-processor) which
> you might be experiencing. Make sure you have the very latest version
> of pg 8.1.x. Also consider checking out 8.2 and see if you can
> reproduce the behavior there...this will require compiling postgresql.
Are these associated with any type of CPU?
Carlo
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-performance@postgresql.org
Cc: stonec.register@sympatico.ca
Subject: Re: commit so slow program looks frozen
In-Reply-To: <ehqsev$18pc$1@news.hub.org>
* 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