From de6a20995ef10ad8d528a14b63d90bc6381cd5c8 Mon Sep 17 00:00:00 2001 From: tilghman Date: Wed, 26 May 2010 16:14:48 +0000 Subject: Construct socket name, according to the Postgres docs, and document as such. (closes issue #17392) Reported by: dps Patches: 20100525__issue17392.diff.txt uploaded by tilghman (license 14) Tested by: dps git-svn-id: http://svn.digium.com/svn/asterisk/trunk@265894 f38db490-d61c-443f-a65b-d21fe96a405b --- configs/res_pgsql.conf.sample | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'configs/res_pgsql.conf.sample') diff --git a/configs/res_pgsql.conf.sample b/configs/res_pgsql.conf.sample index cfb8538bd..b889244a7 100644 --- a/configs/res_pgsql.conf.sample +++ b/configs/res_pgsql.conf.sample @@ -13,6 +13,13 @@ dbname=asterisk dbuser=asterisk dbpass=password ; +; dbsock is specified as the directory where the socket file may be found. The +; actual socket is constructed as a combination of dbsock and dbport. For +; example, the values of '/tmp' and '5432', respectively, will specify a socket +; file of '/tmp/.s.PGSQL.5432'. +; +;dbsock=/tmp +; ; requirements - At startup, each realtime family will make requirements ; on the backend. There are several strategies for handling requirements: ; warn - Warn if the required column does not exist. -- cgit v1.2.3