[MXS-571] Investigation of using PostGres as query classifier. Created: 2016-02-09 Updated: 2016-03-31 Resolved: 2016-03-31 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | None |
| Fix Version/s: | 1.4.1 |
| Type: | Task | Priority: | Major |
| Reporter: | Johan Wikman | Assignee: | Johan Wikman |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Epic Link: | Pluggable Parser |
| Sprint: | 2016-3 |
| Description |
|
PostgreSQL has a nice interface to the parser. List* pg_parse_query(const char* query_string); That is, you provide it with the query string and then you get a list structure that provides information about that query. However, the PostgreSQL code uses setjmp/longjmp for error handling that will not work without modifications in a multi-threaded context. There are also other context variables that clearly will not work without modifications in an MT context. |
| Comments |
| Comment by Johan Wikman [ 2016-02-19 ] |
|
Need to take a second look. |
| Comment by Johan Wikman [ 2016-03-31 ] |
|
We'll first look at sqlite. |