[Pgpool-general] Elusive replication issue

[Tatsuo Ishii]

> 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%.

Oh.

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

For temporary solution, you could change following:

	pool_debug("Query: %s", string);
to:
	pool_log("Query: %s", string);

And run pgpool without -d. This will reduce the debug output.
--
Tatsuo Ishii