- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: brianc/node-postgres
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v7.4.1
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: brianc/node-postgres
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v7.4.2
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 19 commits
- 12 files changed
- 12 contributors
Commits on Jan 10, 2018
-
Configuration menu - View commit details
-
Copy full SHA for be57714 - Browse repository at this point
Copy the full SHA be57714View commit details -
Configuration menu - View commit details
-
Copy full SHA for 94d38f9 - Browse repository at this point
Copy the full SHA 94d38f9View commit details
Commits on Mar 10, 2018
-
The support for the `noAssert` argument dropped in the upcoming Node.js v.10.x. All input is then validated no matter if this is set to true or not. Just remove the argument because of that.
Configuration menu - View commit details
-
Copy full SHA for 3f1d7b9 - Browse repository at this point
Copy the full SHA 3f1d7b9View commit details -
Merge pull request #1585 from BridgeAR/master
Remove `noAssert` argument
Configuration menu - View commit details
-
Copy full SHA for 50b1221 - Browse repository at this point
Copy the full SHA 50b1221View commit details
Commits on Mar 14, 2018
-
use net.Socket instead of net.Stream
`net.Stream` is a undocumented legacy naming from node 0.x https://github.com/nodejs/node/blob/4ae320f2b3c745402955019d6a57a22ee2b8d3bd/lib/net.js#L1762
Configuration menu - View commit details
-
Copy full SHA for 875236f - Browse repository at this point
Copy the full SHA 875236fView commit details -
Merge pull request #1592 from chentsulin/patch-1
use net.Socket instead of net.Stream
Configuration menu - View commit details
-
Copy full SHA for 87dd65f - Browse repository at this point
Copy the full SHA 87dd65fView commit details
Commits on Apr 4, 2018
-
2
Configuration menu - View commit details
-
Copy full SHA for 8fb641e - Browse repository at this point
Copy the full SHA 8fb641eView commit details
Commits on May 4, 2018
-
Configuration menu - View commit details
-
Copy full SHA for b0c60cf - Browse repository at this point
Copy the full SHA b0c60cfView commit details -
Configuration menu - View commit details
-
Copy full SHA for 272e9a5 - Browse repository at this point
Copy the full SHA 272e9a5View commit details -
Configuration menu - View commit details
-
Copy full SHA for 860928e - Browse repository at this point
Copy the full SHA 860928eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 0902d14 - Browse repository at this point
Copy the full SHA 0902d14View commit details -
Handle SSL negotiation errors more robustly
This commit adds some finer grained detail to handling the postmaster's response to SSL negotiation packets, by accounting for the possibility of an 'E' byte being sent back, and emitting an appropriate error. In the naive case, the postmaster will respond with either 'S' (proceed with an SSL connection) or 'N' (SSL is not supported). However, the current if statement doesn't account for an 'E' byte being returned by the postmaster, where an error is encountered (perhaps unable to fork due to being out of memory). By adding this case, we can prevent confusing error messages when SSL is enforced and the postmaster returns an error after successful SSL connections. This also brings the connection handling further in line with libpq, where 'E' is handled similarly as of this commit: postgres/postgres@a49fbaa Given that there are no longer pre-7.0 databases out in the wild, I believe this is a safe change to make, and should not break backwards compatibility (unless matching on error message content). * Replace if statement with switch, to catch 'S', 'E' and 'N' bytes returned by the postmaster * Return an Error for non 'S' or 'N' cases * Expand and restructure unit tests for SSL negotiation packets
Configuration menu - View commit details
-
Copy full SHA for 5d32be4 - Browse repository at this point
Copy the full SHA 5d32be4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7dd3b50 - Browse repository at this point
Copy the full SHA 7dd3b50View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3eb7375 - Browse repository at this point
Copy the full SHA 3eb7375View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9389527 - Browse repository at this point
Copy the full SHA 9389527View commit details -
This happened to work before because `Query.portalName` was undefined, but in order to be able to set the portal explicitly it should be using `Query.portal`.
Configuration menu - View commit details
-
Copy full SHA for 831dfb1 - Browse repository at this point
Copy the full SHA 831dfb1View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4905471 - Browse repository at this point
Copy the full SHA 4905471View commit details -
Configuration menu - View commit details
-
Copy full SHA for 72db790 - Browse repository at this point
Copy the full SHA 72db790View commit details -
Configuration menu - View commit details
-
Copy full SHA for 83ede28 - Browse repository at this point
Copy the full SHA 83ede28View commit details
There are no files selected for viewing