From: | Gerd König <koenig(at)transporeon(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | pgpool-II question |
Date: | 2009-01-23 12:24:39 |
Message-ID: | 4979B707.8030402@transporeon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hello,
while evaluating pgpool-II (replication mode) I ran into a situation
where I don't know the reason why....
The setup looks like:
---------------------
host "one": postgres8.3.5 (defined as backend_0) and pgpoolII (port 9999)
host "two": postgres8.3.5 (defined as backend_1)
According to the tutorial I created database "bench_replication" and
inserted dummy data => everything's fine
In the next step I wanted to create some error scenarios:
a) shutdown "two" while a running update statement
aa) psql -p 9999 bench_replication
ab) update history set tid=<whatever>;
ac) while the update is running, kill postgres on host "two"
=> pgpool got noticed about that and cancelled the update
b) shutdown "one" while statement is running
ba) psql -p 9999 bench_replication
bb) update history set tid=<whatever>;
bc) kill postgres on host "one" (same host where pgpool is running)
=> nothing happens, psql never ends the statement, even no debug entry
in the logfile of pgpool...?!?!?!
why doesn't pgpool recognize that postgres isn't running on host "one" ?
Am I missing something..?!?!
any help appreciated....GERD....
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Monnerie | 2009-01-23 12:57:07 | Re: Why is that index not used? |
Previous Message | Chander Ganesan | 2009-01-22 21:52:13 | Re: PostgreSQL's query caching behaviour |