SSL connectivity issues

[didinele]

This seems to be an issue introduced in 0cb2981 (or somewhere in 2.0.0-beta.5) where using a URL for connecting (i.e postgres(urlHere)) works in unexpected manners when it comes to the sslmode query parameter.

Before beta 5 postgres://user:password@host:port/db?sslmode=disable worked just fine.
On beta 5 this leads into any query rejecting with "Server does not support SSL".

I'm not entirely certain if this was intended but nevertheless, it is very breaking.

Interestingly enough, a work-around I found was making the m uppercase, so ?sslMode=disable worked fine.

[porsager]

Ah thank you. Before sslmode=disable wouldn't do anything, but after implementing sslmode=required, the presence of it, even thought it's the string disabled becomes truthy.. I will make a fix asap.

[iby]

@porsager v2.0.0-beta.6 this doesn't seem to be working as expected with the following error:

      Error: the string "Server does not support SSL" was thrown, throw an Error :)
      at processTicksAndRejections (internal/process/task_queues.js:95:5)

Seems like there's a typo, it should be disable not disabled:

postgres/lib/index.js

Line 578 in e3ace38

return x !== 'disabled' && x !== 'false' && x

Get the following when trying to use dbmate:

Error: pq: unsupported sslmode "disabled"; only "require" (default), "verify-full", "verify-ca", and "disable" supported

The official docs also use disable not disabled.