Hi,
As far as I know, pgpool-II waits for [all] backends to commit the SQL
statements (under replication mode) before returning to the client,
right? This means that if, for example, one of the backends is very busy
(100% CPU, etc.), pgpool will experience a delay and so will the
application.
As far as I know, pgpool-II waits for [all] backends to commit the SQL
statements (under replication mode) before returning to the client,
right? This means that if, for example, one of the backends is very busy
(100% CPU, etc.), pgpool will experience a delay and so will the
application. Is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/21/2010 08:31 PM, Tatsuo Ishii wrote:
As far as I know, pgpool-II waits for [all] backends to commit the SQL
statements (under replication mode) before returning to the client,
right? This means that if, for example, one of the backends is
On 06/21/2010 08:31 PM, Tatsuo Ishii wrote:
As far as I know, pgpool-II waits for [all] backends to commit the SQL
statements (under replication mode) before returning to the client,
right? This means that if, for example, one of the backends is very busy
(100% CPU, etc.), pgpool will
On 06/21/2010 10:16 PM, Tatsuo Ishii wrote:
On 06/21/2010 08:31 PM, Tatsuo Ishii wrote:
As far as I know, pgpool-II waits for [all] backends to commit the SQL
statements (under replication mode) before returning to the client,
right? This means that if, for example, one of the backends is
On 06/21/2010 10:16 PM, Tatsuo Ishii wrote:
On 06/21/2010 08:31 PM, Tatsuo Ishii wrote:
As far as I know, pgpool-II waits for [all] backends to commit the SQL
statements (under replication mode) before returning to the client,
right? This means that if, for example, one of the backends is
On 06/21/2010 10:32 PM, Tatsuo Ishii wrote:
On 06/21/2010 10:16 PM, Tatsuo Ishii wrote:
On 06/21/2010 08:31 PM, Tatsuo Ishii wrote:
As far as I know, pgpool-II waits for [all] backends to commit the SQL
statements (under replication mode) before returning to the client,
right? This means
