where is the active pgpoolAdmin repository ?
the CVS one looks old
(last commit from 2008/02/04, while 2.3 released in 08 Dec 2009)
--
Asaf Ohaion
Lingnu Open Source Consulting Ltd
09-7655871 (204), 0547-920828
http://www.lingnu.com
___
Dear Tatsuo,
Thanks, that's a great explanation, very clear.
Maybe you could add it to the pgpool-II manual, in the
Replication section? Just a suggestion.
Thank you!
Aleksey
On Mon, Jun 7, 2010 at 6:00 PM, Tatsuo Ishii is...@sraoss.co.jp wrote:
Hi. We want to have redundancy for our
Here is a complement for that suggestion:
If the statement is INSERT/UPDATE/DELETE, and the number of returned
affected rows differ, degenerate the backends that differ from master
db, without throwing an error to the client (conserve transparency).
Daniel
-Original Message-
From:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/07/2010 10:00 PM, Tatsuo Ishii wrote:
Hi. We want to have redundancy for our database;
is pgpool-II the right tool, with it's replication mode?
We want to have 2 database servers, and if one
dies, our application just goes on using the
Thanks. Actgually the backends that differ from the master are
degenerated is different from the current implementaion. To choose
the victim backend, we use decide by majority. Suppose we have 3
nodes and they return:
Node 0: A
Node 1: B
Node 2: B
Then the victim is Node 0.
Suppose we have 4
without throwing an error to the client part would be extremely hard
to implement since other concurrent sessions might connects to the
victim backend in the middle of processing.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
Yes, pgpool-II exactly works as you described. Plus, with write query
pgpool-II start a transaction if it's not already started by user.
The write order is first A then B (if A is the first one on
pgpool.conf). Commit order is B then A.
If write query fails, pgpool-II aborts the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When set to true, if a SELECT statement returns a result set of records
different between the backends, the backends that differ from most
frequent result set are degenerated. This is only valid if the SELECT
statement is part of a transaction and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/08/2010 10:03 PM, Tatsuo Ishii wrote:
Yes, pgpool-II exactly works as you described. Plus, with write query
pgpool-II start a transaction if it's not already started by user.
The write order is first A then B (if A is the first one on
Thanks.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
When set to true, if a SELECT statement returns a result set of records
different between the backends, the backends that differ from most
frequent result set are
10 matches
Mail list logo
