-
Notifications
You must be signed in to change notification settings - Fork 21
libpq version 10 or above required for authentication #126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Also seeing this issue. I'm on a Mac M1, incidentally; I have latest libpq installed (brew), but I see that this library is bundling libpq 9.x, so I assume that is the issue. |
On windows, to bump the bundled library, tool chain to configure and compile the full PostgreSQL + manual work to excise the libpq part for both 32 bit and 64 bit and further adjustment so that both can be compiled was necessary. This is quite laborious though the logic is clear. I cannot spend that much time right now. On macOS, if you have libpq installed, then compiling from the source in that environment should use that library. The binary package will use the bundled version as there is no standard for libpq availability. |
Found a solution by installing the RPostgres library. |
I've installed the RPostgres and am still experiencing the error. |
Installing |
@tomoakin, do you have time now to resolve this error? With latest CRAN version, RPostgreSQL_0.7-5, I can confirm this error occurs in attempting a Windows connection and not Linux. It is unfortunate Windows and Mac users must revert to other packages to connect to PostgreSQL. Also, I noticed a typo in error messages missing the T in package name: |
Hi,
Using the latest version of RPostgreSQL (0.7-4) on windows I seem to not be able to connect to a Postgres database 14.5 using SCRAM authentication. On attempting to connect, the following error is emitted:
I suspect that this has to do with the fact that the version of libpq packaged with the windows version is out of date.
Do you have any idea how to resolve this? TIA.
The text was updated successfully, but these errors were encountered: