# Refer to the "Client Authentication" section in the

# PostgreSQL documentation for a complete description

# of this file. A short synopsis follows.

# The first field is the connection type: "local" is a Unix-domain socket,

# "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an

# SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket.

# DATABASE can be "all", "sameuser", "samerole", "replication",

# a database name, or a comma-separated list thereof.

# USER can be "all", a user name, a group name prefixed with "+", or

# a comma-separated list thereof. In both the DATABASE and USER fields

# you can also write a file name prefixed with "@" to include names from

# a separate file.

# CIDR-ADDRESS specifies the set of hosts the record matches.

# It is made up of an IP address and a CIDR mask that is an integer

# (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies

# the number of significant bits in the mask. Alternatively, you can write

# an IP address and netmask in separate columns to specify the set of hosts.

# Instead of a CIDR-address, you can write "samehost" to match any of the

# server's own IP addresses, or "samenet" to match any address in any subnet

# that the server is directly connected to.

# METHOD can be "trust", "reject", "md5", "password", "gss", "sspi", "krb5",

# "ident", "pam", "ldap" or "cert". Note that "password" sends passwords

# in clear text; "md5" is preferred since it sends encrypted passwords.

# NAME=VALUE. The available options depend on the different authentication

# methods - refer to the "Client Authentication" section in the documentation

# for a list of which options are available for which authentication methods.

# Database and user names containing spaces, commas, quotes and other special

# characters must be quoted. Quoting one of the keywords "all", "sameuser",

# "samerole" or "replication" makes the name lose its special character,

# and just match a database or username with that name.

# to SIGHUP the postmaster for the changes to take effect. You can use

# "pg_ctl reload" to do that.

# "host" records. In that case you will also need to make PostgreSQL listen

# on a non-local interface via the listen_addresses configuration parameter,

# or via the -i or -h command line switches.

#

# Refer to the PostgreSQL Administrator's Guide, chapter "Client

# Authentication" for a complete description. A short synopsis follows.

# This file controls PostgreSQL username mapping. It maps

# external user names to their corresponding

# PostgreSQL user names. Records are of the form:

# If SYSTEM-USERNAME starts with a slash (/), it will be treated as

# a regular expression. Optionally this can contain a capture (a

# will be substituted for \1 (backslash-one) if present in PG-USERNAME.

# No map names are defined in the default configuration. If all system

# user names and PostgreSQL user names are the same, you don't need

# anything in this file.

# to SIGHUP the postmaster for the changes to take effect. You can use

# "pg_ctl reload" to do that.

"# CAUTION: Configuring the system for local \"trust\" authentication allows\n" \

"# any local user to connect as any PostgreSQL user, including the database\n" \

"# superuser. If you do not trust all your local users, use another\n" \

"# authentication method.\n"