2007-05-07 22:32:50 +00:00
|
|
|
;
|
|
|
|
|
; Sample configuration for res_config_pgsql
|
|
|
|
|
;
|
|
|
|
|
; The value of dbhost may be either a hostname or an IP address.
|
|
|
|
|
; If dbhost is commented out or the string "localhost", a connection
|
|
|
|
|
; to the local host is assumed and dbsock is used instead of TCP/IP
|
|
|
|
|
; to connect to the server.
|
|
|
|
|
;
|
|
|
|
|
[general]
|
|
|
|
|
dbhost=127.0.0.1
|
|
|
|
|
dbport=5432
|
|
|
|
|
dbname=asterisk
|
|
|
|
|
dbuser=asterisk
|
|
|
|
|
dbpass=password
|
2014-07-16 13:55:36 +00:00
|
|
|
;dbappname=asterisk ; Postgres application_name support (optional). Whitespace not allowed.
|
2008-06-05 19:07:27 +00:00
|
|
|
;
|
2010-05-26 16:14:48 +00:00
|
|
|
; 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'.
|
2014-07-17 21:17:28 +00:00
|
|
|
;
|
2010-05-26 16:14:48 +00:00
|
|
|
;dbsock=/tmp
|
|
|
|
|
;
|
2008-06-05 19:07:27 +00:00
|
|
|
; 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.
|
|
|
|
|
; createclose - Create columns as close to the requirements as possible.
|
|
|
|
|
; createchar - Create char columns only
|
|
|
|
|
;
|
|
|
|
|
requirements=warn
|
