On 07/25/2012 11:37 AM, Gary Webster wrote:
This is a cluster issue, not a database issue. So if you have an
idnle in transaction, then it is affecting your JCR schema as well.
OK, how do I track/debug/stop the "idle in transaction"s ?
Well idle in transaction is ALWAYS a code issue.
On Tue, Jul 24, 2012 at 1:41 PM, Joshua D. Drake wrote:
>
> On 07/24/2012 08:58 AM, Gary Webster wrote:
>
>> Hello.
>> Thanks for the response.
>>
>> There are several 'idle in transaction' on this server/app, but to a
>> different db/schema.
>>
>
> This is a cluster issue, not a database issue. S
On 07/25/2012 11:11 AM, Noe Gutierrez wrote:
they work succesfull an the replication too, but when The Master crashes:
1.- How to promote to slave becomes a new Master and
2.- When Old Master restarts:
How to become old master to slave
How To configure failover in general
You are going t
I have installed the following:
Maquina 1 Postgres 9.1 on Fedora 16 this is the Master
Maquina 2 Postgres 9.1 on Fedora 16 this is the slave
they work succesfull an the replication too, but when The Master crashes:
1.- How to promote to slave becomes a new Master and
2.- When Old Master r
