Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
Greenplum
Gpdb
提交
3b5152ca
G
Gpdb
项目概览
Greenplum
/
Gpdb
通知
7
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
Gpdb
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
3b5152ca
编写于
1月 07, 2005
作者:
T
Tom Lane
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Improve comments in sample config files.
上级
ffce35fe
变更
2
隐藏空白更改
内联
并排
Showing
2 changed file
with
31 addition
and
24 deletion
+31
-24
src/backend/libpq/pg_hba.conf.sample
src/backend/libpq/pg_hba.conf.sample
+26
-20
src/backend/libpq/pg_ident.conf.sample
src/backend/libpq/pg_ident.conf.sample
+5
-4
未找到文件。
src/backend/libpq/pg_hba.conf.sample
浏览文件 @
3b5152ca
...
...
@@ -7,50 +7,56 @@
#
# This file controls: which hosts are allowed to connect, how clients
# 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]
# host DATABASE USER CIDR-ADDRESS METHOD [OPTION]
# hostssl 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,
# "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", "samegroup", a database name (or
# a comma-separated list thereof), or a file name prefixed with "@".
# USER can be "all", an actual user name or a group name prefixed with
# "+" or a list containing either.
#
# DATABASE can be "all", "sameuser", "samegroup", 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 (IPv6) or 128(IPv6) inclusive) that specifies
# the number of significant bits in the mask Also, you can use a
# separate IP address and netmask to specify the set of hosts.
# 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
# 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.
#
# 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",
# "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.
# OPTION is the ident map or the name of the PAM service, depending on METHOD.
#
# Database and user names containing spaces, commas, quotes and other special
# characters
can
be quoted. Quoting one of the keywords "all", "sameuser" or
# "samegroup"
makes the name lose its special character, and just match a
# characters
must
be quoted. Quoting one of the keywords "all", "sameuser" or
# "samegroup"
makes the name lose its special character, and just match a
# database or username with that name.
#
# 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
# to SIGHUP the postmaster for the changes to take effect
, or
use
# "pg_ctl reload".
# to SIGHUP the postmaster for the changes to take effect
. You can
use
# "pg_ctl reload"
to do that
.
# Put your actual configuration here
# ----------------------------------
#
# 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
# on a non-local interface via the listen_addresses configuration parameter,
or
# the -i or -h command line switches.
# on a non-local interface via the listen_addresses configuration parameter,
#
or via
the -i or -h command line switches.
#
@authcomment@
...
...
src/backend/libpq/pg_ident.conf.sample
浏览文件 @
3b5152ca
...
...
@@ -11,18 +11,19 @@
#
# 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
# 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
# PG-USERNAME. Multiple maps may be specified in this file and used
# by pg_hba.conf.
#
# 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
# to SIGHUP the postmaster for the changes to take effect
, or
use
# "pg_ctl reload".
# to SIGHUP the postmaster for the changes to take effect
. You can
use
# "pg_ctl reload"
to do that
.
# Put your actual configuration here
# ----------------------------------
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录