doc: Update link to pg_hba.conf documentation

Also rephrase the text a bit so that it doesn't need to be updated for
every authentication method change in PostgreSQL or PgBouncer.

diff --git a/doc/config.md b/doc/config.md
index 0fcd3d4d52c9209c441f401aaeb279160f1915f9..1d06bec42fd5b962c38ac9456e41f0427e49be47 100644 (file)
--- a/doc/config.md
+++ b/doc/config.md
@@ -907,18 +907,16 @@ file from the `pg_shadow` system table.
 
 ## HBA file format
 
-It follows the format of PostgreSQL pg_hba.conf file -
-<http://www.postgresql.org/docs/9.4/static/auth-pg-hba-conf.html>
-
-There are following differences:
+It follows the format of the PostgreSQL `pg_hba.conf` file
+(see <https://www.postgresql.org/docs/current/auth-pg-hba-conf.html>).
 
 * Supported record types: `local`, `host`, `hostssl`, `hostnossl`.
 * Database field: Supports `all`, `sameuser`, `@file`, multiple names.  Not supported: `replication`, `samerole`, `samegroup`.
 * Username field: Supports `all`, `@file`, multiple names.  Not supported: `+groupname`.
 * Address field: Supported IPv4, IPv6.  Not supported: DNS names, domain prefixes.
-* Auth-method field:  Supported methods: `trust`, `reject`, `md5`, `password`, `peer`, `cert`.
-  Not supported: `gss`, `sspi`, `ident`, `ldap`, `radius`, `pam`.
-  Also username map (`map=`) parameter is not supported.
+* Auth-method field: Only methods supported by PgBouncer's `auth_type`
+  are supported, except `any` and `pam`, which only work globally.
+  Username map (`map=`) parameter is not supported.
 
 
 ## Example