View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000154 | Pgpool-II | Bug | public | 2015-10-20 23:38 | 2016-02-17 18:06 |
| Reporter | skaurus | Assigned To | t-ishii | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | open | ||
| Platform | Linux | OS | Centos | OS Version | 7.1.1503 |
| Summary | 0000154: pgpool fails to parse query used by recent versions of DBD::Pg to ping DB | ||||
| Description | In this commit https://github.com/bucardo/dbdpg/commit/95d03c1eb2ba1332935a6a44dcfdf8ed5068c9f5#diff-910bff34a0a9cc85c863b926e3fe02b9 ping query was changed from "SELECT 'DBD::Pg ping test'" to "/* DBD::Pg ping test v3.5.0 */". pgpool-II-94-3.4.3-1 version fails on this new query: "Unable to parse the query: "/* DBD::Pg ping test v3.5.3 */" from client ...". | ||||
| Steps To Reproduce | something in the lines of: use strict; use DBI; use DBD::Pg; my $dbh = DBI->connect($host, $user, $pass) or die DBI::errstr(); warn $dbh->pg_ping(); | ||||
| Tags | No tags attached. | ||||
|
|
I don' know anything about this: pgpool-II-94-3.4.3-1. Anyway... from looking at the source code, someone who wrote pgpool-II parser was too lazy to distinguish an empty query (in your example) from a parse error. Anyway, the message from pgpool-II in your case is just a warning. The empty query reaches to PostgreSQL and there should be no actual problem. I will fix it if I have spare time. |
|
|
I have started a discussion on this [pgpool-hackers: 1359]. |
|
|
Fixed in master and 3.5 stable branch. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-10-20 23:38 | skaurus | New Issue | |
| 2015-10-21 08:49 | t-ishii | Note Added: 0000595 | |
| 2015-10-21 08:49 | t-ishii | Assigned To | => t-ishii |
| 2015-10-21 08:49 | t-ishii | Status | new => assigned |
| 2016-01-27 17:04 | t-ishii | Note Added: 0000641 | |
| 2016-02-17 18:06 | t-ishii | Note Added: 0000646 | |
| 2016-02-17 18:06 | t-ishii | Status | assigned => resolved |
