On Wed, Jun 8, 2011 at 9:32 AM, Tarabas wrote:
> Hello,
>
> the problem just resurfaced and the Wiki page dows not really help
> very much.
>
> When i look into the pg_stat_activity, i only see that the connections
> all state " in transaction".
>
> Is there any way to find out what the transactio
Hello,
the problem just resurfaced and the Wiki page dows not really help
very much.
When i look into the pg_stat_activity, i only see that the connections
all state " in transaction".
Is there any way to find out what the transaction is doing exactly to
be able to debug the Problem?
Best regar
Hi Scott,
SM> Snip. Those are ALL either AccessShareLock (which is very low level
SM> and non-blocking) or virtual tx locks, which again don't block
SM> anything but their own transaction. Nothing there screams "locks!"
SM> for a better view of locks and how they're blocking things you can use
S
On Mon, Jun 6, 2011 at 10:20 AM, Tarabas wrote:
> Hello!
>
> I am currently having a recurring Locking problem on my Postgres 9.0.4
> Database. I had the same Problem on 9.0.1 and updated to 9.0.4 then.
> It worked fine for a while and just resurfaced.
>
> Suddenly it seems as though there is some
On Mon, Jun 6, 2011 at 11:20 AM, Tarabas wrote:
> Hello!
>
> I am currently having a recurring Locking problem on my Postgres 9.0.4
> Database. I had the same Problem on 9.0.1 and updated to 9.0.4 then.
> It worked fine for a while and just resurfaced.
>
> Suddenly it seems as though there is some
Hello!
I am currently having a recurring Locking problem on my Postgres 9.0.4
Database. I had the same Problem on 9.0.1 and updated to 9.0.4 then.
It worked fine for a while and just resurfaced.
Suddenly it seems as though there is some kind of "deadlock" in the
database, which prevents my client
