aboutsummaryrefslogtreecommitdiff
path: root/contrib/jsonb_plpython/sql
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2018-04-02 11:34:52 -0400
committerPeter Eisentraut <peter_e@gmx.net>2018-04-02 11:37:40 -0400
commit2764d5dcfa84d240c901c20ec6e194f72d82b78a (patch)
tree2db3da15bec088237b5b32f83de90c8cc8817e9b /contrib/jsonb_plpython/sql
parent7e0d64c7a57e28fbcf093b6da9310a38367c1d75 (diff)
downloadpostgresql-2764d5dcfa84d240c901c20ec6e194f72d82b78a.tar.gz
postgresql-2764d5dcfa84d240c901c20ec6e194f72d82b78a.zip
Make be-secure-common.c more consistent for future SSL implementations
Recent commit 8a3d9425 has introduced be-secure-common.c, which is aimed at including backend-side APIs that can be used by any SSL implementation. The purpose is similar to fe-secure-common.c for the frontend-side APIs. However, this has forgotten to include check_ssl_key_file_permissions() in the move, which causes a double dependency between be-secure.c and be-secure-openssl.c. Refactor the code in a more logical way. This also puts into light an API which is usable by future SSL implementations for permissions on SSL key files. Author: Michael Paquier <michael@paquier.xyz>
Diffstat (limited to 'contrib/jsonb_plpython/sql')
0 files changed, 0 insertions, 0 deletions