| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | zhouqq(dot)postgres(at)gmail(dot)com |
| Cc: | lukas(at)fittl(dot)com, alvherre(at)2ndquadrant(dot)com, abusinf(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: reparsing query |
| Date: | 2015-04-17 03:15:48 |
| Message-ID: | 20150417.121548.1534671279968369921.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> It is not difficult to output parsed query in some tool readable
> format but it comes with a maintain overhead: once tools rely on it,
> we have to conform to some schema continuously, like the xml/xmlns. Do
> we want to take this? Depends on how far the tools can go with this
> exposed information.
I think part of the problems could be resolved by using adequate API
to the parse tree. For example, pgpool-II imports PostgreSQL's raw
parser to do a query rewriting. The parse tree format could be changed
release by release but essential API for it (for example tree_walker)
is very stable. As a result, the workforce for rewriting rarely needs
to be modified.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2015-04-17 03:35:44 | Re: Optimization for updating foreign tables in Postgres FDW |
| Previous Message | Alvaro Herrera | 2015-04-17 02:41:12 | Re: Supporting src/test/modules in MSVC builds |