[Pgpool-general] client_ilde_limit_in_recovery
Tatsuo Ishii
ishii at sraoss.co.jp
Fri Dec 17 08:30:49 UTC 2010
> 拝啓 Tatsuo,
>
>
>
> How are you?
>
>
>
> While testing pgpool-II 3.0 on two db instances on the same server, I was
> able to get failover and failback to work; however, now I am testing on two
> different servers, and I can’t seem to get the recovery process to get past
> the 2nd stage:
>
>
>
> 4d09172c.e4e|2010-12-15 14:30:02
> EST|postgres|template1|localhost(36827)|LOG: statement: SELECT
> pgpool_recovery('pgpool_recovery_pitr', 'production4', '/data/postgres')
>
> + DATA=/data/postgres
>
> + RECOVERY_TARGET=production4
>
> + RECOVERY_DATA=/data/postgres
>
> + echo 'pitr begin'
>
> pitr begin
>
> + psql -c 'select pg_switch_xlog()' postgres
>
>
>
>
>
> I should see a “pitr complete” that I put in the script for debugging
> purposes, but it’s as if all psql statements are locked out during the 2nd
> stage, which doesn’t make sense from a run stand-point, since I would never
> get past this part.
Did select pg_switch_xlog() succeed? You can check PostgreSQL log with
log_statement turned on.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
> Is there some unusual bug that I see, or some strange race condition in the
> code?
>
>
>
> Thanks!
>
>
>
> お返事お待ちしております。
>
>
>
> 敬具,
>
> Steve
>
More information about the Pgpool-general
mailing list