<div dir="ltr">updated info, after disable cache shmem, error 0200 gone..<div>How to debug this cache behavior? </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Mar 18, 2019 at 7:09 PM milist ujang <<a href="mailto:ujang.milist@gmail.com">ujang.milist@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Hi,<div><br></div><div>It seems "unable to parse" log messages just a warning, even though the query still processed normally.</div><div><br></div><div>Since 0200 error intermittently being occurred, we turn on log_per_node_statement, and grep the log, and luckily users report 0200 when the query was served by cache (query result fetched from cache. statement: select....).</div><div><br></div><div>I got confused with the white_memqcache_table_list parameter, in current online document said that the parameter apply only for views and unlogged tables, but from slide at <a href="https://www.sraoss.co.jp/event_seminar/2012/20121024_pgpool-II_pgconfEU2012_sraoss.pdf" target="_blank">https://www.sraoss.co.jp/event_seminar/2012/20121024_pgpool-II_pgconfEU2012_sraoss.pdf</a> it said table can also be specified in this parameter.</div><div><br></div><div>The table which got 0200 error is not listed in white_memqcache_table_list parameter, also not listed in black_memqcache_table_list parameter; but from the pgpool log, the query to that table served by cache.</div><div><br></div><div><br></div><div><br></div></div></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 15, 2019 at 8:28 PM Tatsuo Ishii <<a href="mailto:ishii@sraoss.co.jp" target="_blank">ishii@sraoss.co.jp</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> Tested in pgpool dev, 2 version of queries:<br>
> A. select * from (select branch_type as A from branch where parent_id in<br>
> (1813) order by branch_id) limit 1;<br>
> B. select * from (select branch_type as A from branch where parent_id in<br>
> (1813) order by branch_id) AS TMP limit 1;<br>
> <br>
> in pgpool log:<br>
> A. there is log error unable to parse query.<br>
> B. no error<br>
<br>
Pgpool-II has an SQL parser which is ported from open source<br>
PostgreSQL, not edb. The query A can only be parsed by edb, not by<br>
either Pgpool-II or PostgreSQL. I bet PostgreSQL will give an error<br>
with A too.<br>
<br>
Best regards,<br>
--<br>
Tatsuo Ishii<br>
SRA OSS, Inc. Japan<br>
English: <a href="http://www.sraoss.co.jp/index_en.php" rel="noreferrer" target="_blank">http://www.sraoss.co.jp/index_en.php</a><br>
Japanese:<a href="http://www.sraoss.co.jp" rel="noreferrer" target="_blank">http://www.sraoss.co.jp</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail-m_-8001791628159051130gmail_signature">regards<br><br>ujang jaenudin | DBA Consultant (Freelancer)<br><a href="http://ora62.wordpress.com" target="_blank">http://ora62.wordpress.com</a><br><a href="http://id.linkedin.com/pub/ujang-jaenudin/12/64/bab" target="_blank">http://id.linkedin.com/pub/ujang-jaenudin/12/64/bab</a></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">regards<br><br>ujang jaenudin | DBA Consultant (Freelancer)<br><a href="http://ora62.wordpress.com" target="_blank">http://ora62.wordpress.com</a><br><a href="http://id.linkedin.com/pub/ujang-jaenudin/12/64/bab" target="_blank">http://id.linkedin.com/pub/ujang-jaenudin/12/64/bab</a></div>