1 |
# PostgreSQL User Name Maps |
2 |
# ========================= |
3 |
# |
4 |
# Refer to the PostgreSQL documentation, chapter "Client |
5 |
# Authentication" for a complete description. A short synopsis |
6 |
# follows. |
7 |
# |
8 |
# This file controls PostgreSQL user name mapping. It maps external |
9 |
# user names to their corresponding PostgreSQL user names. Records |
10 |
# are of the form: |
11 |
# |
12 |
# MAPNAME SYSTEM-USERNAME PG-USERNAME |
13 |
# |
14 |
# (The uppercase quantities must be replaced by actual values.) |
15 |
# |
16 |
# MAPNAME is the (otherwise freely chosen) map name that was used in |
17 |
# pg_hba.conf. SYSTEM-USERNAME is the detected user name of the |
18 |
# client. PG-USERNAME is the requested PostgreSQL user name. The |
19 |
# existence of a record specifies that SYSTEM-USERNAME may connect as |
20 |
# PG-USERNAME. |
21 |
# |
22 |
# If SYSTEM-USERNAME starts with a slash (/), it will be treated as a |
23 |
# regular expression. Optionally this can contain a capture (a |
24 |
# parenthesized subexpression). The substring matching the capture |
25 |
# will be substituted for \1 (backslash-one) if present in |
26 |
# PG-USERNAME. |
27 |
# |
28 |
# Multiple maps may be specified in this file and used by pg_hba.conf. |
29 |
# |
30 |
# No map names are defined in the default configuration. If all |
31 |
# system user names and PostgreSQL user names are the same, you don't |
32 |
# need anything in this file. |
33 |
# |
34 |
# This file is read on server startup and when the postmaster receives |
35 |
# a SIGHUP signal. If you edit the file on a running system, you have |
36 |
# to SIGHUP the postmaster for the changes to take effect. You can |
37 |
# use "pg_ctl reload" to do that. |
38 |
|
39 |
# Put your actual configuration here |
40 |
# ---------------------------------- |
41 |
|
42 |
# MAPNAME SYSTEM-USERNAME PG-USERNAME |
43 |
local root postgres |