Skip site navigation (1) Skip section navigation (2)

[PATCH] pgpassfile connection option

From: Julian Markwort <julian(dot)markwort(at)uni-muenster(dot)de>
To: pgsql-hackers(at)postgresql(dot)org
Subject: [PATCH] pgpassfile connection option
Date: 2016-09-22 14:44:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Hello psql-hackers!

We thought it would be advantageous to be able to specify a 'custom' 
pgpassfile within the connection string along the lines of the existing 
parameters sslkey and sslcert.

Which is exactly what this very compact patch does.
The patch is minimally invasive - when no pgpassfile attribute is 
provided in the connection string, the regular pgpassfile is used.
The security-measures (which are limited to checking the permissions for 
0600) are kept, however we could loosen that restriciton to allow group 
access as well along the lines of the ssl key file , if this is 
preferred. (in case multiple users belonging to the same group would 
like to connect using the same file).

The patch applies cleanly to master and compiles and runs as expected 
(as there are no critical alterations).
I've not written any documentation as of now, but I'll follow up closely 
if there is any interest for this patch.

  - using ~ to denote the user's home directory in the path does not 
work, however $HOME works (as this is translated by bash beforehand).
  - the notation in the custom pgpassfile should follow the notation of 
the 'default' pgpass files:
  - this has only been tested on linux so far, however due to the nature 
of the changes I suspect that there is nothing that could go wrong in 
other environments, although I could test that as well, if deemed necessary.

I'm looking forward to any feedback,


Julian Markwort
Westphalian Wilhelms-University in Münster

Attachment: pgpassfile-v1.patch
Description: text/x-patch (3.2 KB)


pgsql-hackers by date

Next:From: Andrew DunstanDate: 2016-09-22 15:15:45
Subject: Re: [PATCH] pgpassfile connection option
Previous:From: Tom LaneDate: 2016-09-22 14:11:20
Subject: Re: Executor's internal ParamExecData Params versus EvalPlanQual

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group