Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
3b5152ca
Commit
3b5152ca
authored
20 years ago
by
Tom Lane
Browse files
Options
Downloads
Patches
Plain Diff
Improve comments in sample config files.
parent
ffce35fe
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
src/backend/libpq/pg_hba.conf.sample
+26
-20
26 additions, 20 deletions
src/backend/libpq/pg_hba.conf.sample
src/backend/libpq/pg_ident.conf.sample
+5
-4
5 additions, 4 deletions
src/backend/libpq/pg_ident.conf.sample
with
31 additions
and
24 deletions
src/backend/libpq/pg_hba.conf.sample
+
26
−
20
View file @
3b5152ca
...
@@ -7,50 +7,56 @@
...
@@ -7,50 +7,56 @@
#
#
# This file controls: which hosts are allowed to connect, how clients
# This file controls: which hosts are allowed to connect, how clients
# are authenticated, which PostgreSQL user names they can use, which
# are authenticated, which PostgreSQL user names they can use, which
# databases they can access. Records take one of
seven
forms:
# databases they can access. Records take one of
these
forms:
#
#
# local DATABASE USER METHOD [OPTION]
# local DATABASE USER METHOD [OPTION]
# host DATABASE USER CIDR-ADDRESS METHOD [OPTION]
# host DATABASE USER CIDR-ADDRESS METHOD [OPTION]
# hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTION]
# hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTION]
# hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTION]
# hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTION]
#
#
# (The uppercase quantities should be replaced by actual values.)
# (The uppercase items must be replaced by actual values.)
#
# The first field is the connection type: "local" is a Unix-domain socket,
# 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
# "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.
# SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket.
# DATABASE can be "all", "sameuser", "samegroup", a database name (or
#
# a comma-separated list thereof), or a file name prefixed with "@".
# DATABASE can be "all", "sameuser", "samegroup", a database name, or
# USER can be "all", an actual user name or a group name prefixed with
# a comma-separated list thereof.
# "+" or a list containing either.
#
# 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.
# 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
# It is made up of an IP address and a CIDR mask that is an integer
# (between 0 and 32 (IPv6) or 128(IPv6) inclusive) that specifies
# (between 0 and 32 (IPv6) or 128(IPv6) inclusive) that specifies
# the number of significant bits in the mask Also, you can use a
# the number of significant bits in the mask. Alternatively, you can write
# separate IP address and netmask to specify the set of hosts.
# an IP address and netmask in separate columns to specify the set of hosts.
#
# METHOD can be "trust", "reject", "md5", "crypt", "password",
# "krb4", "krb5", "ident", or "pam". Note that "password" sends passwords
# in clear text; "md5" is preferred since it sends encrypted passwords.
#
#
# METHOD can be "trust", "reject", "md5", "crypt", "password",
# OPTION is the ident map or the name of the PAM service, depending on METHOD.
# "krb4", "krb5", "ident", or "pam". Note that "password" uses
# clear-text passwords; "md5" is preferred for encrypted passwords.
# OPTION is the ident map or the name of the PAM service.
#
#
# Database and user names containing spaces, commas, quotes and other special
# Database and user names containing spaces, commas, quotes and other special
# characters
can
be quoted. Quoting one of the keywords "all", "sameuser" or
# characters
must
be quoted. Quoting one of the keywords "all", "sameuser" or
# "samegroup"
makes the name lose its special character, and just match a
# "samegroup" makes the name lose its special character, and just match a
# database or username with that name.
# database or username with that name.
#
#
# This file is read on server startup and when the postmaster receives
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal. If you edit the file on a running system, you have
# a SIGHUP signal. If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect
, or
use
# to SIGHUP the postmaster for the changes to take effect
. You can
use
# "pg_ctl reload".
# "pg_ctl reload"
to do that
.
# Put your actual configuration here
# Put your actual configuration here
# ----------------------------------
# ----------------------------------
#
#
# If you want to allow non-local connections, you need to add more
# If you want to allow non-local connections, you need to add more
# "host" records. In that case you will also need to make PostgreSQL listen
# "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
# on a non-local interface via the listen_addresses configuration parameter,
# the -i or -h command line switches.
#
or via
the -i or -h command line switches.
#
#
@authcomment@
@authcomment@
...
...
This diff is collapsed.
Click to expand it.
src/backend/libpq/pg_ident.conf.sample
+
5
−
4
View file @
3b5152ca
...
@@ -11,18 +11,19 @@
...
@@ -11,18 +11,19 @@
#
#
# MAPNAME IDENT-USERNAME PG-USERNAME
# MAPNAME IDENT-USERNAME PG-USERNAME
#
#
# (The uppercase quantities should be replaced by actual values.)
# (The uppercase quantities must be replaced by actual values.)
#
# MAPNAME is the (otherwise freely chosen) map name that was used in
# MAPNAME is the (otherwise freely chosen) map name that was used in
# pg_hba.conf. IDENT-USERNAME is the detected user name of the
# pg_hba.conf. IDENT-USERNAME is the detected user name of the
# client. PG-USERNAME is the request PostgreSQL user name. The
# client. PG-USERNAME is the request
ed
PostgreSQL user name. The
# existence of a record specifies that IDENT-USERNAME may connect as
# existence of a record specifies that IDENT-USERNAME may connect as
# PG-USERNAME. Multiple maps may be specified in this file and used
# PG-USERNAME. Multiple maps may be specified in this file and used
# by pg_hba.conf.
# by pg_hba.conf.
#
#
# This file is read on server startup and when the postmaster receives
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal. If you edit the file on a running system, you have
# a SIGHUP signal. If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect
, or
use
# to SIGHUP the postmaster for the changes to take effect
. You can
use
# "pg_ctl reload".
# "pg_ctl reload"
to do that
.
# Put your actual configuration here
# Put your actual configuration here
# ----------------------------------
# ----------------------------------
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment