Potential fix for client_encoding error #291
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'll get on the failed test ASAP - in the meantime I'd still like to know some others' thoughts on this. |
|
Looks good to me |
brianc
added a commit
that referenced
this pull request
Mar 7, 2013
Potential fix for client_encoding error
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
error: unrecognized configuration parameter "lient_encoding"
at p.parseE (/xx/node_modules/pg/lib/connection.js:503:11)
at p.parseMessage (/xx/node_modules/pg/lib/connection.js:363:17)
at CleartextStream.p.attachListeners (/xx/node_modules/pg/lib/connection.js:90:18)
at CleartextStream.EventEmitter.emit (events.js:96:17)
at CleartextStream.CryptoStream._push (tls.js:540:12)
at SecurePair.cycle (tls.js:898:20)
at EncryptedStream.CryptoStream.write (tls.js:285:13)
at Socket.ondata (stream.js:38:26)
at Socket.EventEmitter.emit (events.js:96:17)
at TCP.onread (net.js:397:14)
http://www.postgresql.org/docs/current/static/libpq-connect.html also looks like this should be specified more like "client_encoding 'utf8'" rather than "options --client_encoding='utf8'"
Feel free to shoot me down if this is completely off. I'm testing with OS X as a client and psql 9.1 on OpenBSD as a server.