options

precedence evidence

The following environment variables can be used to select default connection parameter values, which will be used by PQconnectdb , PQsetdbLogin and PQsetdb if no value is directly specified by the calling code. These are useful to avoid hard-coding database connection information into simple client applications, for example., Service names can be defined in either a per-user service file or a system-wide file. If the same service name exists in both the user and the system file, the user file takes precedence. By default, the per-user service file is named ~/.pg_service.conf . On Microsoft Windows, it is named %APPDATA%\postgresql\.pg_service.conf (where %APPDATA% refers to the Application Data subdirectory in the user's profile). A different file name can be specified by setting the environment variable PGSERVICEFILE . The system-wide file is named pg_service.conf . By default it is sought in the etc directory of the PostgreSQL installation (use pg_config --sysconfdir to identify this directory precisely). Another directory, but not a different file name, can be specified by setting the environment variable PGSYSCONFDIR ., Connection parameters obtained from a service file are combined with parameters obtained from other sources. A service file setting overrides the corresponding environment variable, and in turn can be overridden by a value given directly in the connection string. For example, using the above service file, a connection string service=mydb port=5434 will use host somehost , port 5434 , user admin , and other parameters as set by environment variables or built-in defaults.

source option

{"compiled_default_expression":"DefaultOption","declaration":"\"options\", \"PGOPTIONS\", DefaultOption, NULL, \"Backend-Options\", \"\", 40, offsetof(struct pg_conn, pgoptions)","environment":"PGOPTIONS","keyword":"options","source_notes":["ssl options are allowed even without client SSL support because the client can still handle SSL modes \"disable\" and \"allow\". Other parameters have no effect on non-SSL connections, so there is no reason to exclude them since none of them are mandatory.","As with SSL, all GSS options are exposed even in builds that don't have support."]}