[pgpool-hackers: 1668] Re: kind does not match error in pgpool

Tatsuo Ishii ishii at postgresql.org
Thu Jun 30 17:51:42 JST 2016


Usama,

> Totally agreed on both the points. I think you have a valid point and
> unconditionally forwarding all the kind = N messages to frontend is the
> best choice. The attached version 2 of the patch does the same as suggested.

Thanks for the patch. BTW, I had hard time to test the patch. The
original problem report was talking about VACUUM case, but in
streaming replication mode, VACUUM is sent to primary node only and
kind mismatch error can't happend with VACUUM command.

Any suggestion to trigger kind mismatch errors in streaming
replication mode?

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp


More information about the pgpool-hackers mailing list