From 89f3cd8f8bddc7806cd6a5f7a81db34fbea5b622 Mon Sep 17 00:00:00 2001 From: Marko Kreen Date: Wed, 28 Mar 2012 00:01:13 +0300 Subject: [PATCH] config.txt: Postgres does not use auth files anymore. Clarify documentation on the matter and hint how to generate the file automatically. --- doc/config.txt | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/doc/config.txt b/doc/config.txt index 8592e10..aae3cb0 100644 --- a/doc/config.txt +++ b/doc/config.txt @@ -550,18 +550,23 @@ Ask specific +timezone+ from server. == AUTHENTICATION FILE FORMAT == PgBouncer needs its own user database. The users are loaded from a text -file that should be in same format as PostgreSQL's +pg_auth/pg_pwd+ -file. +file in following format: "username1" "password" ... "username2" "md5abcdef012342345" ... There should be at least 2 fields, surrounded by double quotes. The first field is the username and the second is either a plain-text or a MD5-hashed -password. PgBouncer ignores the rest of the line. +password. PgBouncer ignores the rest of the line. + +This file format is equivalent to text files used by PostgreSQL 8.x +for authentication info, thus allowing PgBouncer to work directly +on PostgreSQL authentication files in data directory. + +Since PostgreSQL 9.0, the text files are not used anymore. Thus the +auth file needs to be generated. See `./etc/mkauth.py` for sample script +to generate auth file from `pg_shadow` table. -This file format allows you to directly use the existing PostgreSQL -authentication files in the PostgreSQL data directory. == EXAMPLE == -- 2.40.0