{"action":"reopened","issue":{"number":49,"created_at":"2011-09-14T21:10:57Z","pull_request":{"diff_url":null,"patch_url":null,"html_url":null},"body":"This problem only came up with Node 0.5.6.  I send a request to a postgresql database, wait a minute, and then send another request.  It breaks.\r\n\r\nTry the following code:\r\n\r\n    var pg = require('pg'),\r\n        util = require('util');\r\n    var connectstring = 'pg://postgres:1234@127.0.0.1/postgres';\r\n\r\n    function getTheTime() {\r\n      pg.connect(connectstring, function (err, client) {\r\n        client.query('SELECT now() as when', function (err, result) {\r\n          util.log('The postres time is: ' + result.rows[0].when);\r\n        });\r\n      });\r\n    }\r\n\r\n    getTheTime();\r\n    setTimeout(getTheTime, 60 * 1000);\r\n\r\nThe first `getTheTime` works fine, and the second `getTheTime` throws the following error:\r\n\r\n    node.js:203\r\n            throw e; // process.nextTick error, or 'error' event on first tick\r\n                  ^\r\n    Error: read UNKNOWN\r\n        at errnoException (net_uv.js:557:11)\r\n        at TCP.onread (net_uv.js:326:20)\r\n\r\nI am running Node 0.5.6 on Windows.  It only happens with a delay between the two requests.  Sending requests repeatedly works fine.  Therefore, some new feature in Node 0.5.6 must be dropping the connection?","comments":6,"title":"Connection pool broken in Node 0.5.6?","updated_at":"2011-10-16T19:51:23Z","url":"https://api.github.com/repos/brianc/node-postgres/issues/49","id":1647611,"assignee":null,"milestone":null,"closed_at":null,"user":{"gravatar_id":"5c6e86938b5b628a79bede426dbc7b63","avatar_url":"https://secure.gravatar.com/avatar/5c6e86938b5b628a79bede426dbc7b63?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","url":"https://api.github.com/users/chowey","id":991221,"login":"chowey"},"html_url":"https://github.com/brianc/node-postgres/issues/49","labels":[],"state":"open"},"legacy":{"number":49,"action":"reopened","issue":1647611}}