[pgpool-general: 6467] Re: Unable to parse the query

milist ujang ujang.milist at gmail.com
Mon Mar 18 21:09:45 JST 2019


Hi,

It seems "unable to parse" log messages just a warning, even though the
query still processed normally.

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

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
https://www.sraoss.co.jp/event_seminar/2012/20121024_pgpool-II_pgconfEU2012_sraoss.pdf
it said table can also be specified in this parameter.

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.




On Fri, Feb 15, 2019 at 8:28 PM Tatsuo Ishii <ishii at sraoss.co.jp> wrote:

> > Tested in pgpool dev, 2 version of queries:
> > A. select * from (select branch_type as A from branch where parent_id in
> > (1813) order by branch_id) limit 1;
> > B. select * from (select branch_type as A from branch where parent_id in
> > (1813) order by branch_id) AS TMP limit 1;
> >
> > in pgpool log:
> > A. there is log error unable to parse query.
> > B. no error
>
> Pgpool-II has an SQL parser which is ported from open source
> PostgreSQL, not edb. The query A can only be parsed by edb, not by
> either Pgpool-II or PostgreSQL. I bet PostgreSQL will give an error
> with A too.
>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
>


-- 
regards

ujang jaenudin | DBA Consultant (Freelancer)
http://ora62.wordpress.com
http://id.linkedin.com/pub/ujang-jaenudin/12/64/bab
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20190318/8dbcc0e7/attachment.html>


More information about the pgpool-general mailing list