sysconfdir = @sysconfdir@
sharedstatedir = @sharedstatedir@
docdir = @docdir@
+mandir = @mandir@
top_builddir = @top_builddir@
srcdir = @srcdir@
xmlto man $<
%.xml: %.txt
- asciidoc -b docbook -d manpage $<
+ asciidoc -b docbook -d manpage -o - $< \
+ | python fixman.py > $@
%.html: %.txt
asciidoc -a toc $<
--- /dev/null
+#! /usr/bin/env python
+import sys,re
+# add empty <simpara> after <literallayout> to force line break
+sys.stdout.write(re.sub(r"</literallayout>\s+<simpara>", r"\g<0></simpara><simpara>", sys.stdin.read()))
Basic setup and usage as following.
-This example assumes the +postgres+ user is given administrative
-permissions from +pgbouncer.ini+ and that +pgbouncer+ is configured to
-be listening on +localhost:6543+.
-
1. Create config file. Details in +pgbouncer(5)+. Simplest:
[databases]
- template1 = host=127.0.0.1 dbname=template1
+ template1 = host=127.0.0.1 port=5432 dbname=template1
[pgbouncer]
listen_port = 6543
==== max_client_conn ====
-Maximum number of client connections allowed.
+Maximum number of client connections allowed. When increased then the file
+descriptor limits should also be increased. Note that actual number of file
+descriptiors used is more that max_client_conn. Theoretical maximum used is:
+
+ max_client_conn * max_pool_size * total_databases * total_users
+
+if each user connects under it's own username to server. If database user
+is specified in connect string (all users connect under same username),
+the theoretical maximum is:
+
+ max_client_conn * max_pool_size * total_databases
+
+The theoretical maximum is never reaches, unless somebody deliberately
+crafts special load for it. Still, it means you should give fds liberately.
+
+Search for `ulimit` in your favourite shell man page.
Default: 100
then issue rollback and keep it
* suspend_timeout - drop stalled conns
* rename disable_varcache to track_parameters
+ * some preliminary notification that fd limit is full
== Ver 1.0.9 ==