Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 1b43743

Browse filesBrowse files
committed
Add description for new patterns supported in HBA and ident sample files
Support for regexps in database and role entries for pg_hba.conf has been added in 8fea868, and efb6f4a has extended support of pg-user in pg_ident.conf, still both of them have missed a short description about the new patterns supported in their respective sample files. This commit closes the gap, by providing a short description of all the new features supported for each entry type. Reported-by: Pavel Luzanov Reviewed-by: Jelte Fennema, Pavel Luzanov Discussion: https://postgr.es/m/e495112d-8741-e651-64a2-ecb5728f1a56@postgrespro.ru
1 parent fd923b5 commit 1b43743
Copy full SHA for 1b43743

File tree

2 files changed

+13
-8
lines changed
Filter options

2 files changed

+13
-8
lines changed

‎src/backend/libpq/pg_hba.conf.sample

Copy file name to clipboardExpand all lines: src/backend/libpq/pg_hba.conf.sample
+9-8Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -31,14 +31,15 @@
3131
# - "hostnogssenc" is a TCP/IP socket that is not GSSAPI-encrypted
3232
#
3333
# DATABASE can be "all", "sameuser", "samerole", "replication", a
34-
# database name, or a comma-separated list thereof. The "all"
35-
# keyword does not match "replication". Access to replication
36-
# must be enabled in a separate record (see example below).
37-
#
38-
# USER can be "all", a user name, a group name prefixed with "+", or a
39-
# comma-separated list thereof. In both the DATABASE and USER fields
40-
# you can also write a file name prefixed with "@" to include names
41-
# from a separate file.
34+
# database name, a regular expression (if it starts with a slash (/))
35+
# or a comma-separated list thereof. The "all" keyword does not match
36+
# "replication". Access to replication must be enabled in a separate
37+
# record (see example below).
38+
#
39+
# USER can be "all", a user name, a group name prefixed with "+", a
40+
# regular expression (if it starts with a slash (/)) or a comma-separated
41+
# list thereof. In both the DATABASE and USER fields you can also write
42+
# a file name prefixed with "@" to include names from a separate file.
4243
#
4344
# ADDRESS specifies the set of hosts the record matches. It can be a
4445
# host name, or it is made up of an IP address and a CIDR mask that is

‎src/backend/libpq/pg_ident.conf.sample

Copy file name to clipboardExpand all lines: src/backend/libpq/pg_ident.conf.sample
+4Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,10 @@
2929
# will be substituted for \1 (backslash-one) if present in
3030
# PG-USERNAME.
3131
#
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+
#
3236
# Multiple maps may be specified in this file and used by pg_hba.conf.
3337
#
3438
# No map names are defined in the default configuration. If all

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.