[Pgpool-general] Elusive replication issue

[Josh Berkus]

Tatsuo,

> You are misunderstanding. Checking is always
> enabled. replication_stop_on_mistmatch controls the behavoir after an
> error is found. i.e. if it's true, failover/degenration
> happens. Otherwise the child process just exits.
>
> > Unfortunately, we only seem to be able to produce this issue through
> > intense activity, which makes collecting debug output rather difficult.
>
> An idea is set replication_strict to true.

This would degrade our performance badly, like 50%.

Is there any way to see what pgpool thinks is mismatched?  Aside from 
collecting a 200MB debug file?

-- 
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco