From: | ALEXANDER JOSE <aangelj(at)hotmail(dot)com> |
---|---|
To: | postgres admin <pgsql-admin(at)postgresql(dot)org>, Postgres Español <pgsql-es-ayuda(at)postgresql(dot)org> |
Subject: | Status DISCARD ALL |
Date: | 2016-02-19 02:39:17 |
Message-ID: | COL129-W8021542A62B62033C91C9FA5A00@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-es-ayuda |
Our platform consists of two servers with database postgresql v9.3, v3.3 pgpool for high availability on debian OS v7, and we have many connections webserver servers. The problem is presented when down two servers in weblogic that are clustered, and the pgpool connection status discard all remain, making it impossible to back up both servers WebLogic, to solve it we must lower the pgpool of each nodes so that sessions that were to discard all canceled status and weblogic can start and open connections without error.
We would like to know if there are any configuration parameter that can kill pgpool sessions remaining discard all status.
Alexander Angel
DAB Postgresql
Venezuela
From | Date | Subject | |
---|---|---|---|
Next Message | Horacio Miranda | 2016-02-19 03:16:30 | Re: [pgsql-es-ayuda] Status DISCARD ALL |
Previous Message | nunks | 2016-02-19 02:02:30 | ANALYZE'ing table hierarchies |
From | Date | Subject | |
---|---|---|---|
Next Message | Horacio Miranda | 2016-02-19 03:16:30 | Re: [pgsql-es-ayuda] Status DISCARD ALL |
Previous Message | Horacio Miranda | 2016-02-19 01:50:58 | Re: [pgsql-es-ayuda] [OFFTOPIC] - Espacio en disco de tablas con imágenes. |