View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000341 | Pgpool-II | Bug | public | 2017-09-23 03:28 | 2017-09-23 06:32 |
| Reporter | sobrinho | Assigned To | |||
| Priority | high | Severity | block | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Product Version | 3.6.2 | ||||
| Fixed in Version | 3.6.6 | ||||
| Summary | 0000341: Incompatibility with ruby pg | ||||
| Description | I'm not sure this is a problem with pg gem or pgpoll-ii. The problem happens with that code: require 'pg' conn = PG.connect(dbname: 'itsalive', port: 9999) conn.async_exec('select 1', []) The process freezes and it can be stopped with CTRL+C, the only way to kill the process is using CTRL-Z + kill -9 %1. Using a direct connection to the master database it works as expected by returning the result. The same problem happens when using exec instead of async_exec. I'm going to cross-post this issue on ruby pg to be sure (pg 0.21.0). | ||||
| Tags | No tags attached. | ||||
|
|
To clarify, not sending the empty array on the second argument fixes the problem. |
|
|
On pgpool 3.6.6 the problem doesn't happen. Closing. |
|
|
Thanks for the info. Issue closed. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-09-23 03:28 | sobrinho | New Issue | |
| 2017-09-23 03:29 | sobrinho | Note Added: 0001712 | |
| 2017-09-23 06:18 | sobrinho | Note Added: 0001713 | |
| 2017-09-23 06:31 | t-ishii | Note Added: 0001714 | |
| 2017-09-23 06:32 | t-ishii | Status | new => closed |
| 2017-09-23 06:32 | t-ishii | Fixed in Version | => 3.6.6 |
