| 1 | # PostgreSQL User Name Maps |
| 2 | # ========================= |
| 3 | # |
| 4 | # --------------- |
| 5 | # Mapping Records |
| 6 | # --------------- |
| 7 | # |
| 8 | # Refer to the PostgreSQL documentation, chapter "Client |
| 9 | # Authentication" for a complete description. A short synopsis |
| 10 | # follows. |
| 11 | # |
| 12 | # This file controls PostgreSQL user name mapping. It maps external |
| 13 | # user names to their corresponding PostgreSQL user names. Records |
| 14 | # are of the form: |
| 15 | # |
| 16 | # MAPNAME SYSTEM-USERNAME PG-USERNAME |
| 17 | # |
| 18 | # (The uppercase quantities must be replaced by actual values.) |
| 19 | # |
| 20 | # MAPNAME is the (otherwise freely chosen) map name that was used in |
| 21 | # pg_hba.conf. SYSTEM-USERNAME is the detected user name of the |
| 22 | # client. PG-USERNAME is the requested PostgreSQL user name. The |
| 23 | # existence of a record specifies that SYSTEM-USERNAME may connect as |
| 24 | # PG-USERNAME. |
| 25 | # |
| 26 | # If SYSTEM-USERNAME starts with a slash (/), it will be treated as a |
| 27 | # regular expression. Optionally this can contain a capture (a |
| 28 | # parenthesized subexpression). The substring matching the capture |
| 29 | # will be substituted for \1 (backslash-one) if present in |
| 30 | # PG-USERNAME. |
| 31 | # |
| 32 | # PG-USERNAME can be "all", a user name, a group name prefixed with "+", or |
| 33 | # a regular expression (if it starts with a slash (/)). If it is a regular |
| 34 | # expression, the substring matching with \1 has no effect. |
| 35 | # |
| 36 | # Multiple maps may be specified in this file and used by pg_hba.conf. |
| 37 | # |
| 38 | # No map names are defined in the default configuration. If all |
| 39 | # system user names and PostgreSQL user names are the same, you don't |
| 40 | # need anything in this file. |
| 41 | # |
| 42 | # --------------- |
| 43 | # Include Records |
| 44 | # --------------- |
| 45 | # |
| 46 | # This file allows the inclusion of external files or directories holding |
| 47 | # more records, using the following keywords: |
| 48 | # |
| 49 | # include FILE |
| 50 | # include_if_exists FILE |
| 51 | # include_dir DIRECTORY |
| 52 | # |
| 53 | # FILE is the file name to include, and DIR is the directory name containing |
| 54 | # the file(s) to include. Any file in a directory will be loaded if suffixed |
| 55 | # with ".conf". The files of a directory are ordered by name. |
| 56 | # include_if_exists ignores missing files. FILE and DIRECTORY can be |
| 57 | # specified as a relative or an absolute path, and can be double-quoted if |
| 58 | # they contain spaces. |
| 59 | # |
| 60 | # ------------------------------- |
| 61 | # Miscellaneous |
| 62 | # ------------------------------- |
| 63 | # |
| 64 | # This file is read on server startup and when the postmaster receives |
| 65 | # a SIGHUP signal. If you edit the file on a running system, you have |
| 66 | # to SIGHUP the postmaster for the changes to take effect. You can |
| 67 | # use "pg_ctl reload" to do that. |
| 68 | |
| 69 | # Put your actual configuration here |
| 70 | # ---------------------------------- |
| 71 | |
| 72 | # MAPNAME SYSTEM-USERNAME PG-USERNAME |
huncholane