pool-general: 1315] Re: [GENERAL] Database connections seemingly
hanging
> It seems that the root cause was that pgpool acquired the locks in the
> wrong order. If the resource is called A it seems that pgpool allows
child
> X to acquire A on node1 and at the same time, child Y
> It seems that the root cause was that pgpool acquired the locks in the
> wrong order. If the resource is called A it seems that pgpool allows child
> X to acquire A on node1 and at the same time, child Y acquires A on node2.
> This leaves X wanting A on node2 and Y wanting A on node1. This lea
4
netstat -p on 10.216.73.204: http://pastebin.com/tPz8gwRG
Kind regards,
Fredrik & friends
Tom Lane
2013/01/10 05:30
To
fredrik.huitfeldtmad...@schneider-electric.com
cc
pgsql-general@postgresql.org, pgpool-gene...@pgpool.net
Subject
Re: [GENERAL] Database connections seemingly hanging
f
fredrik.huitfeldtmad...@schneider-electric.com writes:
> We have a setup where 2 JBoss (5.1) servers communicate with 1 instance of
> PgPool (3.04), which again communicates with 2 Postgresql (8.4) servers.
> The JBoss servers host some Java code for us and as part of that they run
> some quartz
