{"issue":{"state":"open","pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"milestone":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/395e8552961b8bbfbcf23e3bbeafd2bd?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"395e8552961b8bbfbcf23e3bbeafd2bd","url":"https://api.github.com/users/cbbrowne","login":"cbbrowne","id":325762},"assignee":null,"labels":[],"updated_at":"2011-10-31T22:48:43Z","closed_at":null,"comments":4,"url":"https://api.github.com/repos/lxn/go-pgsql/issues/6","body":"I'll observe that another Go/PG binding is on GitHub, <https://github.com/jbarham/pgsql.go>, which take the alternative approach of wrapping libpq.  \r\n\r\nIt handles the thread safety issue by implementing a connection pool mechanism.\r\n\r\nI don't know if it's a better thing to try to merge code in one direction or another; I simply observe that it's worth taking a peek at it to see what's worth adapting in either direction.","html_url":"https://github.com/lxn/go-pgsql/issues/6","title":"Pools...","number":6,"id":1958252,"created_at":"2011-10-18T17:27:40Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/395e8552961b8bbfbcf23e3bbeafd2bd?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"395e8552961b8bbfbcf23e3bbeafd2bd","url":"https://api.github.com/users/cbbrowne","login":"cbbrowne","id":325762},"updated_at":"2011-10-31T22:48:43Z","url":"https://api.github.com/repos/lxn/go-pgsql/issues/comments/2584493","body":"Actually, here's an attempt at .pgpass...\r\n\r\nhttps://github.com/cbbrowne/go-pgsql/commit/b849b6f6b8556c533370dd47dc4d8b022db56fe0","id":2584493,"created_at":"2011-10-31T22:48:43Z"}}