| 
									
										
										
										
											2007-05-07 22:32:50 +00:00
										 |  |  | ; | 
					
						
							|  |  |  | ; Sample configuration for res_config_pgsql | 
					
						
							|  |  |  | ; | 
					
						
							| 
									
										
										
										
											2025-01-08 23:00:39 +01:00
										 |  |  | ; The value of hostname may be either a hostname or an IP address. | 
					
						
							|  |  |  | ; If hostname is commented out or the string "localhost", a connection | 
					
						
							| 
									
										
										
										
											2007-05-07 22:32:50 +00:00
										 |  |  | ; to the local host is assumed and dbsock is used instead of TCP/IP | 
					
						
							|  |  |  | ; to connect to the server. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | [general] | 
					
						
							| 
									
										
										
										
											2025-01-08 23:00:39 +01:00
										 |  |  | ;hostname=localhost | 
					
						
							|  |  |  | ;port=5432 | 
					
						
							|  |  |  | ;dbname=asterisk | 
					
						
							|  |  |  | ;user=postgres | 
					
						
							|  |  |  | ;password=password | 
					
						
							|  |  |  | ;appname=asterisk    ; Postgres application_name support (optional). Whitespace not allowed. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | ; socket is specified as the directory where the socket file may be found. The | 
					
						
							|  |  |  | ; actual socket is constructed as a combination of socket and port.  For | 
					
						
							| 
									
										
										
										
											2010-05-26 16:14:48 +00:00
										 |  |  | ; example, the values of '/tmp' and '5432', respectively, will specify a socket | 
					
						
							|  |  |  | ; file of '/tmp/.s.PGSQL.5432'. | 
					
						
							| 
									
										
										
										
											2017-12-22 09:23:22 -05:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											2025-01-08 23:00:39 +01:00
										 |  |  | ;socket=/tmp | 
					
						
							| 
									
										
										
										
											2010-05-26 16:14:48 +00:00
										 |  |  | ; | 
					
						
							| 
									
										
										
										
											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 | 
					
						
							| 
									
										
										
										
											2023-07-12 12:03:59 -04:00
										 |  |  | 
 | 
					
						
							|  |  |  | ; When multiple rows are requested by realtime, res_config_pgsql will add an | 
					
						
							|  |  |  | ; explicit ORDER BY clause to the generated SELECT statement. To prevent | 
					
						
							|  |  |  | ; that from occuring, set order_multi_row_results_by_initial_column to 'no'. | 
					
						
							|  |  |  | ; | 
					
						
							|  |  |  | ;order_multi_row_results_by_initial_column=no |