9

I am using R on Windows to connect to a PostgreSQL database hosted on AWS. The database is set up using forcessl = 1 - this means that any connection needs to be set up with sslmode=require.

The base RPostgreSQL package does not provide any exposure to ssl options. This has been raised as an issue many times (see here, here, here and here)

I know there is a workaround using the RPostgres package, but for other functionality reasons I would much prefer to use the RPostgreSQL package.

A few answers (e.g. here) have proposed using a modified dbname to connect with ssl like so:

dbConnect(dbDriver('PostgreSQL'),
    dbname   = 'dbname=foobar sslmode=require', # modified dbname
    host     = 'foobar.rds.amazonaws.com',
    port     = 5439,
    user     = 'foobar',
    password = 'foobar')

But this did not work for me using the CRAN version of the package. This led me to a recent issue raised on the RPostgreSQL github: https://github.com/tomoakin/RPostgreSQL/issues/88

The initial user was able to use the modified dbname method when he compiled the package from source. On Windows, using the latest source package (0.6.2) compiled with RTools, I get the following error when I run the modified dbname code:

Error in postgresqlNewConnection(drv, ...) : 
  RS-DBI driver: (could not connect xxxxx.rds.amazonawss.com:5432 on dbname "xxxxxxx": sslmode value "require" invalid when SSL support is not compiled in
)

From this and the rest of the thread, it looks like SSL is not possible from current source in both Windows and Mac. However, the developer suggests:

If you compile in a environment where libssl and libpq was made SSL activated form, then the driver can use SSL.

I think this means I could manually download the libs and compile myself, but I am not sure if it is a quick fix or if it would require significant rewriting of the package. Any help or pointing in the right direction would be much appreciated. How can I do this in a safe, repeatable way?

Chris
  • 6,302
  • 1
  • 27
  • 54
  • Did you manage to solve your problem on Windows ? – Julien Navarre Apr 10 '18 at 16:39
  • @JulienNavarre no unfortunately not. See here: https://github.com/tomoakin/RPostgreSQL/issues/88#issuecomment-333765712 What is needed is to write a configure.win file in the package – Chris Apr 11 '18 at 14:54

2 Answers2

4

I was able to solve this for the El Capitan macOS R users in my office, by doing the following:

  • Remove RPostgreSQL R package if you already have installed. Methods vary on how to do this, but from either R.app console or R in Terminal, type remove.packages('RPostgreSQL')

  • Make sure you have Homebrew installed, and from Terminal run: brew install libpq openssl

  • Open R.app, and from the Packages & Data menu, select Package Installer.

  • From the first drop-down menu, choose CRAN (sources) (choose mirror closest to you if you haven't used this before).

  • Using package search, find RPostgreSQL and for the options below, keep At System Level checked, and check Install Dependencies, then click Install Selected.

  • Quit out of all R and RStudio programs, and try using the new from source installed RPostgreSQL package.

DISCLAIMER: If you have heavy compile dependencies on OpenSSL or libpq for other programs, I have no idea how doing the above may break other programs.

Sena Heydari
  • 63
  • 6
  • Thank you, but I very much need this solved on Windows – Chris Feb 16 '18 at 20:44
  • I also had to install the `postgresql` package via Brew before re-installing/rebuilding the `RPostgreSQL` package in order to get SSL support to work. – Alex May 22 '20 at 20:25
2

Building on Windows is a can of worms. See R-Admin Windows Toolset. The only openSSL binaries for windows are from unknown developers. Building and installing openSSL on windows is another can of worms that you will need to research. It might be easier to install openSSL inside the R Windows build environment, but I have no experience with that.

EDIT: It turns out that when installing postgres on Windows, postgres installs openSSL. That means that the central problem on Windows is installing the Windows Toolset for R, installing postgres, then pointing the R build system to libpq.

Another solution would be to run linux in a virtual machine under windows. Here is one way to Install linux on Windows. With linux, depending on the distribution, you would only need to do something like the following from the linux command line (for a RedHat variant of linux):

sudo yum install openSSL
sudo yum install postgresql96
sudo yum install R

Line 2 installs libpq which is required for RPostgreSQL. It is libpq which must be compiled with openSSL. You will only be installing and using the PostgreSQL client, not the server and will also get psql. There might be other packages required, see R linux toolset. Normally, these will get pulled in with the above and should not be a problem.

RPostgreSQL contains a version of libpq, but the compile script does not look like it checks for openSSL, at least not on macOS. So it is important to get a system provided libpq installed.

It is also important for the RPostgreSQL configure script to find pg_config, which is installed when postgres client is installed. Not sure about windows through. So make sure pg_config is in your path. Type pg_config to find out.

Now you need to download and compile RPostgreSQL. To start R, type the following at the linux terminal.

R

Then from within R, get, compile and install RPostgreSQL:

install.packages("https://cran.r-project.org/src/contrib/RPostgreSQL_0.6-2.tar.gz", repo=NULL, type="source")

This should compile and install this version of RPostgreSQL. This last line should also work in windows if you have the windows tools installed correctly.

Hopefully, this gives you some ideas.

Neil
  • 601
  • 7
  • 16
  • After looking at this a bit more, openssl does not seem to be the issue, as it is compiled into the default Windows installation from EnterpriseDB. However, when installing from source on Windows, the package stubbornly uses the bundled libpq instead of the pre-installed one (even though pg_config is in my PATH). I think fixing this issue (or finding a workaround) is the last step to solve – Chris Sep 18 '17 at 14:45
  • The R path may be different than the OS path. You need to make sure the R path contains pg_config. See https://www.biostat.wisc.edu/~kbroman/Rintro/Rwinpack.html – Neil Sep 19 '17 at 15:13
  • In my case from the R GUI, `Sys.getenv("PATH")` did not return the location of `pg_config.exe`. – Neil Sep 19 '17 at 15:37
  • You might try something along the lines of `path <- paste(Sys.getenv("PATH"), "C:\\Program Files\\PostgreSQL\\9.6\\bin", collapse=";")` `Sys.setenv(PATH = path)` in the R GUI. – Neil Sep 19 '17 at 16:07
  • No dice - pg_config was already in my PATH and it still used the bundled version. Since the `configure.win` file in the RPostgreSQL is empty and there are no references to Windows in the `configure` file, I feel like compiling from an existing `libpq` installation is not working on Windows. – Chris Sep 19 '17 at 16:58