{"Entry":{"collection":"conn","key":"sslrootcert","name":"sslrootcert","aliases":["PGSSLROOTCERT","sslrootcert"],"metadata":{"aliases":["PGSSLROOTCERT","sslrootcert"],"category":"TLS","content_hash":"2c0994dd3adb475606af3a64a82b143300b1afbbed3991668e7d174975c9261b","derived_content_hash":"946872bbe57a0f8abbe4d1aa644b07869bf2fc811eabe90522bbaf48c40c0f5a","documentation_refresh":{"batch":"20261113","original_source_rev":"","versions":{"14":"14.25","15":"15.20","16":"16.16","17":"17.12","18":"18.7","19":"19rc2"}},"imported_at":"2026-09-30T00:40:35.169055+08:00","name":"sslrootcert","name_zh":"","slug":"sslrootcert","summary":"This parameter specifies the name of a file containing SSL certificate authority ( CA ) certificate(s). If the file exists, the server's certificate will be verified to be signed by one of these authorities. The default is ~/.postgresql/root.crt ."}},"Definition":{"Collection":"conn","Key":"sslrootcert","SourceDatabase":"center","Version":"18","SourceTable":"connection_parameter","SourceKey":"sslrootcert","SourceRevision":"ee8d1a3612338fd9adf250730cb640fcc5233b5491337cc00a316a44e3a0b9f8","Facts":{"comparison_data":{"compiled_default_expression":"NULL","default_evidence":["This parameter specifies the name of a file containing SSL certificate authority ( CA ) certificate(s). If the file exists, the server's certificate will be verified to be signed by one of these authorities. The default is ~/.postgresql/root.crt .","When using sslrootcert=system , the default sslmode is changed to verify-full , and any weaker setting will result in an error. In most cases it is trivial for anyone to obtain a certificate trusted by the system for a hostname they control, rendering verify-ca and all weaker modes useless."],"definition":"This parameter specifies the name of a file containing SSL certificate authority ( CA ) certificate(s). If the file exists, the server's certificate will be verified to be signed by one of these authorities. The default is ~/.postgresql/root.crt . The special value system may be specified instead, in which case the trusted CA roots from the SSL implementation will be loaded. The exact locations of these root certificates differ by SSL implementation and platform. For OpenSSL in particular, the locations may be further modified by the SSL_CERT_DIR and SSL_CERT_FILE environment variables. Note When using sslrootcert=system , the default sslmode is changed to verify-full , and any weaker setting will result in an error. In most cases it is trivial for anyone to obtain a certificate trusted by the system for a hostname they control, rendering verify-ca and all weaker modes useless. The magic system value will take precedence over a local certificate file with the same name. If for some reason you find yourself in this situation, use an alternative path like sslrootcert=./system instead.","documented":true,"environment":"PGSSLROOTCERT","keyword":"sslrootcert"},"comparison_hash":"cfaf4586de024c51c1f0e01892077feddab5b492ce218160353456e11a6799e1","default_evidence":["This parameter specifies the name of a file containing SSL certificate authority ( CA ) certificate(s). If the file exists, the server's certificate will be verified to be signed by one of these authorities. The default is ~/.postgresql/root.crt .","When using sslrootcert=system , the default sslmode is changed to verify-full , and any weaker setting will result in an error. In most cases it is trivial for anyone to obtain a certificate trusted by the system for a hostname they control, rendering verify-ca and all weaker modes useless."],"description":["This parameter specifies the name of a file containing SSL certificate authority ( CA ) certificate(s). If the file exists, the server's certificate will be verified to be signed by one of these authorities. The default is ~/.postgresql/root.crt ."],"description_zh":"此参数指定包含 SSL 证书颁发机构（ CA ）证书的文件名。如果文件存在，则会验证服务器证书是否由这些机构之一签名。默认值为 ~/.postgresql/root.crt 。 也可以指定特殊值 system ，此时会加载 SSL 实现提供的受信任 CA 根证书。这些根证书的确切位置因 SSL 实现和平台而异。对于 OpenSSL ，还可以通过 SSL_CERT_DIR 和 SSL_CERT_FILE 环境变量进一步修改这些位置。 注意 使用 sslrootcert=system 时，默认的 sslmode 会改为 verify-full ，任何较弱的设置都会引发错误。在大多数情况下，任何人都很容易为其控制的主机名获取受系统信任的证书，因此 verify-ca 及所有更弱的模式都无法发挥作用。 特殊值 system 优先于同名的本地证书文件。如果遇到这种情况，请改用其他路径，例如 sslrootcert=./system 。","description_zh_html":"\u003cp\u003e连接参数 sslrootcert。\u003c/p\u003e\u003ch3\u003e同版本中文手册定义\u003c/h3\u003e\u003cdd\u003e\u003cp\u003e\n        此参数指定包含 SSL 证书颁发机构（\u003cacronym class=\"acronym\"\u003eCA\u003c/acronym\u003e）证书的文件名。如果文件存在，则会验证服务器证书是否由这些机构之一签名。默认值为 \u003ccode class=\"filename\"\u003e~/.postgresql/root.crt\u003c/code\u003e。\n       \u003c/p\u003e\u003cp\u003e\n        也可以指定特殊值 \u003ccode class=\"literal\"\u003esystem\u003c/code\u003e，此时会加载 SSL 实现提供的受信任 CA 根证书。这些根证书的确切位置因 SSL 实现和平台而异。对于 \u003cspan class=\"productname\"\u003eOpenSSL\u003c/span\u003e，还可以通过 \u003ccode class=\"envar\"\u003eSSL_CERT_DIR\u003c/code\u003e 和 \u003ccode class=\"envar\"\u003eSSL_CERT_FILE\u003c/code\u003e 环境变量进一步修改这些位置。\n       \u003c/p\u003e\u003cdiv class=\"note\"\u003e\u003ch3 class=\"title\"\u003e注意\u003c/h3\u003e\u003cp\u003e\n        使用 \u003ccode class=\"literal\"\u003esslrootcert=system\u003c/code\u003e 时，默认的 \u003ccode class=\"literal\"\u003esslmode\u003c/code\u003e 会改为 \u003ccode class=\"literal\"\u003everify-full\u003c/code\u003e，任何较弱的设置都会引发错误。在大多数情况下，任何人都很容易为其控制的主机名获取受系统信任的证书，因此 \u003ccode class=\"literal\"\u003everify-ca\u003c/code\u003e 及所有更弱的模式都无法发挥作用。\n       \u003c/p\u003e\u003cp\u003e\n        特殊值 \u003ccode class=\"literal\"\u003esystem\u003c/code\u003e 优先于同名的本地证书文件。如果遇到这种情况，请改用其他路径，例如 \u003ccode class=\"literal\"\u003esslrootcert=./system\u003c/code\u003e。\n       \u003c/p\u003e\u003c/div\u003e\u003c/dd\u003e\u003cp\u003e\u003ca href=\"/zh/docs/18/libpq-connect.html#LIBPQ-CONNECT-SSLROOTCERT\"\u003e查看完整中文手册与上下文\u003c/a\u003e。\u003c/p\u003e","documented":true,"environment":[{"description":"PGSSLROOTCERT behaves the same as the sslrootcert connection parameter.","name":"PGSSLROOTCERT","source_url":"/docs/18/libpq-envars.html"}],"facts":[{"label":"Client library","value":"libpq 18.6"},{"label":"Manual definition","value":"Documented"},{"label":"Source environment fallback","value":"PGSSLROOTCERT"},{"label":"Compiled fallback expression","value":"NULL"}],"facts_zh":[{"label":"客户端库","value":"libpq 18.6"},{"label":"手册定义","value":"手册已记载"},{"label":"源码中的环境变量回退","value":"PGSSLROOTCERT"},{"label":"编译时回退表达式","value":"NULL"}],"keyword":"sslrootcert","manual_html":"\u003cdiv\u003e\u003cdl class=\"variablelist\"\u003e\u003cdt id=\"LIBPQ-CONNECT-SSLROOTCERT\"\u003e\u003cspan class=\"term\"\u003e\u003ccode class=\"literal\"\u003esslrootcert\u003c/code\u003e\u003c/span\u003e \u003c/dt\u003e\u003cdd\u003e\n\u003cp\u003eThis parameter specifies the name of a file containing SSL certificate authority (CA) certificate(s). If the file exists, the server's certificate will be verified to be signed by one of these authorities. The default is \u003ccode class=\"filename\"\u003e~/.postgresql/root.crt\u003c/code\u003e.\u003c/p\u003e\n\u003cp\u003eThe special value \u003ccode class=\"literal\"\u003esystem\u003c/code\u003e may be specified instead, in which case the trusted CA roots from the SSL implementation will be loaded. The exact locations of these root certificates differ by SSL implementation and platform. For \u003cspan class=\"productname\"\u003eOpenSSL\u003c/span\u003e in particular, the locations may be further modified by the \u003ccode class=\"envar\"\u003eSSL_CERT_DIR\u003c/code\u003e and \u003ccode class=\"envar\"\u003eSSL_CERT_FILE\u003c/code\u003e environment variables.\u003c/p\u003e\n\u003cdiv class=\"note\"\u003e\n\u003ch3 class=\"title\"\u003eNote\u003c/h3\u003e\n\u003cp\u003eWhen using \u003ccode class=\"literal\"\u003esslrootcert=system\u003c/code\u003e, the default \u003ccode class=\"literal\"\u003esslmode\u003c/code\u003e is changed to \u003ccode class=\"literal\"\u003everify-full\u003c/code\u003e, and any weaker setting will result in an error. In most cases it is trivial for anyone to obtain a certificate trusted by the system for a hostname they control, rendering \u003ccode class=\"literal\"\u003everify-ca\u003c/code\u003e and all weaker modes useless.\u003c/p\u003e\n\u003cp\u003eThe magic \u003ccode class=\"literal\"\u003esystem\u003c/code\u003e value will take precedence over a local certificate file with the same name. If for some reason you find yourself in this situation, use an alternative path like \u003ccode class=\"literal\"\u003esslrootcert=./system\u003c/code\u003e instead.\u003c/p\u003e\n\u003c/div\u003e\n\u003c/dd\u003e\u003c/dl\u003e\u003c/div\u003e","manual_path":"libpq-connect.html#LIBPQ-CONNECT-SSLROOTCERT","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."],"related":[{"label":"Connection service file","url":"/docs/18/libpq-pgservice.html"},{"label":"Password file","url":"/docs/18/libpq-pgpass.html"},{"label":"All libpq environment variables","url":"/docs/18/libpq-envars.html"}],"release":{"channel":"stable","evidence_kind":"English manual and source declarations","label":"18.6","major":"18","manifest":{"index":"index.html","major":"18","pages":1148,"pdf":{"A4":{"built_at":"2026-09-26","bytes":15865106,"pages":3154,"sha256":"19512c405da53f9f7fcf0abba359223aa65f021be025bf3411381918f92e3190","url":"/files/documentation/pdf/18/postgresql-18-A4.pdf"},"US":{"built_at":"2026-09-26","bytes":15748059,"pages":3328,"sha256":"facbe6c229e598b872d3d98bef53308f46e06746006fa4590de9a7de9dd46319","url":"/files/documentation/pdf/18/postgresql-18-US.pdf"}},"release":"18.6","source_mode":"en SGML built with pinned official archive","source_sha256":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","source_url":"https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2","svg_assets":3,"tree":"18"},"ref":"https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2","revision":"ee8d1a3612338fd9adf250730cb640fcc5233b5491337cc00a316a44e3a0b9f8","source_sha256":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"},"sections":[{"paragraphs":["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."],"title":"Default resolution and service-file precedence"},{"paragraphs":["PGSSLROOTCERT behaves the same as the sslrootcert connection parameter."],"title":"Environment variable evidence"}],"sections_zh":[{"paragraphs":["以下环境变量可用于选择连接参数的默认值，供 PQconnectdb 、 PQsetdbLogin 和 PQsetdb 在调用代码未直接指定参数值时使用。例如，这样可以避免在简单的客户端应用程序中硬编码数据库连接信息。","服务名称可以在每个用户的服务文件或系统范围的文件中定义。如果同一个服务名称存在于用户文件和系统文件中，则用户文件优先。默认情况下，每个用户的服务文件名为 ~/.pg_service.conf 。在Microsoft Windows上，它的名称为 %APPDATA%\\postgresql\\.pg_service.conf （其中 %APPDATA% 指用户配置文件夹中的应用数据子目录）。可以通过设置环境变量 PGSERVICEFILE 来指定不同的文件名。系统范围的文件名为 pg_service.conf 。默认情况下，在 PostgreSQL 安装的 etc 目录中寻找（使用 pg_config --sysconfdir 来准确识别此目录）。可以通过设置环境变量 PGSYSCONFDIR 来指定另一个目录，但不能指定不同的文件名。","从服务文件中获取的连接参数会与其他来源的参数合并。服务文件中的设置会覆盖相应的环境变量，而连接字符串中直接给出的值又会覆盖服务文件中的设置。例如，使用上述服务文件时，连接字符串 service=mydb port=5434 将使用主机 somehost 、端口 5434 、用户 admin ，以及由环境变量或内置默认值设置的其他参数。"],"title":"默认值解析与服务文件优先级"},{"paragraphs":["PGSSLROOTCERT 的行为与 sslrootcert 连接参数相同。"],"title":"环境变量证据"}],"signature":"sslrootcert","source_option":{"compiled_default_expression":"NULL","declaration":"\"sslrootcert\", \"PGSSLROOTCERT\", NULL, NULL, \"SSL-Root-Certificate\", \"\", 64, offsetof(struct pg_conn, sslrootcert)","environment":"PGSSLROOTCERT","keyword":"sslrootcert","source_notes":[]},"sources":[{"anchor":"LIBPQ-CONNECT-SSLROOTCERT","file":"libpq-connect.html","label":"18.6 English manual · libpq-connect.html","sha256":"c26a7fc3dcda6066cfe540641ae2690faf3d3c03277f30b4dfc2328ab45c212f","url":"/docs/18/libpq-connect.html#LIBPQ-CONNECT-SSLROOTCERT"},{"archive_sha256":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","file":"src/interfaces/libpq/fe-connect.c","label":"18.6 libpq connection option declarations","sha256":"44a6e386cbfd67ebe768d6ef5493098119c2e6b4796239d53e5ed7b122b206a5","url":"https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2"},{"anchor":"","file":"libpq-envars.html","label":"18.6 English manual · libpq-envars.html","sha256":"d64db73f3d48127bb984a5f775e77b7bcca2ba4bd218333cf24a45fcdd7c4363","url":"/docs/18/libpq-envars.html"},{"anchor":"","file":"libpq-pgservice.html","label":"18.6 English manual · libpq-pgservice.html","sha256":"6035a3f0ee1d0fd80db5bf58834390b884eecd23206659bdf6f07560deea5aa7","url":"/docs/18/libpq-pgservice.html"}],"tables":[{"columns":[{"key":"name","label":"Variable"},{"key":"description","label":"Documented behavior"}],"key":"environment","rows":[{"description":"PGSSLROOTCERT behaves the same as the sslrootcert connection parameter.","name":{"text":"PGSSLROOTCERT","url":"/docs/18/libpq-envars.html"}}],"title":"Environment fallback"}],"tables_zh":[{"columns":[{"key":"name","label":"变量"},{"key":"description","label":"手册记载的行为"}],"key":"environment","rows":[{"description":"PGSSLROOTCERT 的行为与 sslrootcert 连接参数相同。","name":{"text":"PGSSLROOTCERT","url":"/docs/18/libpq-envars.html"}}],"title":"环境变量回退"}],"zh_from":{"authored_translation":"source-derived-identity","body_sha256":"a652ee9237085479abf481e88117cefc36e5745cc09acbffd04cddb1c187fc97","kind":"same-version-chinese-manual-with-source-derived-identity","manual":{"anchor":"LIBPQ-CONNECT-SSLROOTCERT","build_id":107,"extraction":"exact-definition","fragment_sha256":"a990c9cfc0104bb315db2e0a24d2a02883fd4229610fd37ecb1ec2cf2e4be4ce","locale":"zh-Hans","page_key":"libpq-connect.html","source_hash":"1555b03a2bc480920a9c72be9683ee3ddf99e8a5c17267c0dca73c42cd50e44c","source_revision":"unknown:rendered-translation-baseline","translated_from_revision":null,"translation_revision":"git:b1b500221dbe5437cfca004d6b04d3f6e422765d;html-sha256:08e987a66af27b98444a8057c256314eafa13611a3fb9e888214fc436824244b","url":"/zh/docs/18/libpq-connect.html#LIBPQ-CONNECT-SSLROOTCERT","version":"18"},"runtime_rerun":false,"source_facts_revision":"ee8d1a3612338fd9adf250730cb640fcc5233b5491337cc00a316a44e3a0b9f8"}},"ManualEvidence":{"manual_path":"libpq-connect.html#LIBPQ-CONNECT-SSLROOTCERT","release":{"channel":"stable","evidence_kind":"English manual and source declarations","label":"18.6","major":"18","manifest":{"index":"index.html","major":"18","pages":1148,"pdf":{"A4":{"built_at":"2026-09-26","bytes":15865106,"pages":3154,"sha256":"19512c405da53f9f7fcf0abba359223aa65f021be025bf3411381918f92e3190","url":"/files/documentation/pdf/18/postgresql-18-A4.pdf"},"US":{"built_at":"2026-09-26","bytes":15748059,"pages":3328,"sha256":"facbe6c229e598b872d3d98bef53308f46e06746006fa4590de9a7de9dd46319","url":"/files/documentation/pdf/18/postgresql-18-US.pdf"}},"release":"18.6","source_mode":"en SGML built with pinned official archive","source_sha256":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","source_url":"https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2","svg_assets":3,"tree":"18"},"ref":"https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2","revision":"ee8d1a3612338fd9adf250730cb640fcc5233b5491337cc00a316a44e3a0b9f8","source_sha256":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f"},"sources":[{"anchor":"LIBPQ-CONNECT-SSLROOTCERT","file":"libpq-connect.html","label":"18.6 English manual · libpq-connect.html","sha256":"c26a7fc3dcda6066cfe540641ae2690faf3d3c03277f30b4dfc2328ab45c212f","url":"/docs/18/libpq-connect.html#LIBPQ-CONNECT-SSLROOTCERT"},{"archive_sha256":"555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f","file":"src/interfaces/libpq/fe-connect.c","label":"18.6 libpq connection option declarations","sha256":"44a6e386cbfd67ebe768d6ef5493098119c2e6b4796239d53e5ed7b122b206a5","url":"https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2"},{"anchor":"","file":"libpq-envars.html","label":"18.6 English manual · libpq-envars.html","sha256":"d64db73f3d48127bb984a5f775e77b7bcca2ba4bd218333cf24a45fcdd7c4363","url":"/docs/18/libpq-envars.html"},{"anchor":"","file":"libpq-pgservice.html","label":"18.6 English manual · libpq-pgservice.html","sha256":"6035a3f0ee1d0fd80db5bf58834390b884eecd23206659bdf6f07560deea5aa7","url":"/docs/18/libpq-pgservice.html"}]},"MeasuredEvidence":{}},"Text":{"Collection":"conn","Key":"sslrootcert","SourceDatabase":"center","Version":"18","Locale":"en","Title":"sslrootcert","Summary":"This parameter specifies the name of a file containing SSL certificate authority ( CA ) certificate(s). If the file exists, the server's certificate will be verified to be signed by one of these authorities. The default is ~/.postgresql/root.crt .","BodyHTML":"\u003cdiv\u003e\u003cdl\u003e\u003cdt id=\"LIBPQ-CONNECT-SSLROOTCERT\"\u003e\u003cspan\u003e\u003ccode\u003esslrootcert\u003c/code\u003e\u003c/span\u003e \u003c/dt\u003e\u003cdd\u003e\n\u003cp\u003eThis parameter specifies the name of a file containing SSL certificate authority (CA) certificate(s). If the file exists, the server\u0026#39;s certificate will be verified to be signed by one of these authorities. The default is \u003ccode\u003e~/.postgresql/root.crt\u003c/code\u003e.\u003c/p\u003e\n\u003cp\u003eThe special value \u003ccode\u003esystem\u003c/code\u003e may be specified instead, in which case the trusted CA roots from the SSL implementation will be loaded. The exact locations of these root certificates differ by SSL implementation and platform. For \u003cspan\u003eOpenSSL\u003c/span\u003e in particular, the locations may be further modified by the \u003ccode\u003eSSL_CERT_DIR\u003c/code\u003e and \u003ccode\u003eSSL_CERT_FILE\u003c/code\u003e environment variables.\u003c/p\u003e\n\u003cdiv\u003e\n\u003ch3\u003eNote\u003c/h3\u003e\n\u003cp\u003eWhen using \u003ccode\u003esslrootcert=system\u003c/code\u003e, the default \u003ccode\u003esslmode\u003c/code\u003e is changed to \u003ccode\u003everify-full\u003c/code\u003e, and any weaker setting will result in an error. In most cases it is trivial for anyone to obtain a certificate trusted by the system for a hostname they control, rendering \u003ccode\u003everify-ca\u003c/code\u003e and all weaker modes useless.\u003c/p\u003e\n\u003cp\u003eThe magic \u003ccode\u003esystem\u003c/code\u003e value will take precedence over a local certificate file with the same name. If for some reason you find yourself in this situation, use an alternative path like \u003ccode\u003esslrootcert=./system\u003c/code\u003e instead.\u003c/p\u003e\n\u003c/div\u003e\n\u003c/dd\u003e\u003c/dl\u003e\u003c/div\u003e","SourceRevision":"ee8d1a3612338fd9adf250730cb640fcc5233b5491337cc00a316a44e3a0b9f8","ContentHash":"becf15677599e588dcf096d46f0f7817314b306971d976672ce716e89d1673a1","Payload":{"description":["This parameter specifies the name of a file containing SSL certificate authority ( CA ) certificate(s). If the file exists, the server's certificate will be verified to be signed by one of these authorities. The default is ~/.postgresql/root.crt ."],"manual_html":"\u003cdiv\u003e\u003cdl class=\"variablelist\"\u003e\u003cdt id=\"LIBPQ-CONNECT-SSLROOTCERT\"\u003e\u003cspan class=\"term\"\u003e\u003ccode class=\"literal\"\u003esslrootcert\u003c/code\u003e\u003c/span\u003e \u003c/dt\u003e\u003cdd\u003e\n\u003cp\u003eThis parameter specifies the name of a file containing SSL certificate authority (CA) certificate(s). If the file exists, the server's certificate will be verified to be signed by one of these authorities. The default is \u003ccode class=\"filename\"\u003e~/.postgresql/root.crt\u003c/code\u003e.\u003c/p\u003e\n\u003cp\u003eThe special value \u003ccode class=\"literal\"\u003esystem\u003c/code\u003e may be specified instead, in which case the trusted CA roots from the SSL implementation will be loaded. The exact locations of these root certificates differ by SSL implementation and platform. For \u003cspan class=\"productname\"\u003eOpenSSL\u003c/span\u003e in particular, the locations may be further modified by the \u003ccode class=\"envar\"\u003eSSL_CERT_DIR\u003c/code\u003e and \u003ccode class=\"envar\"\u003eSSL_CERT_FILE\u003c/code\u003e environment variables.\u003c/p\u003e\n\u003cdiv class=\"note\"\u003e\n\u003ch3 class=\"title\"\u003eNote\u003c/h3\u003e\n\u003cp\u003eWhen using \u003ccode class=\"literal\"\u003esslrootcert=system\u003c/code\u003e, the default \u003ccode class=\"literal\"\u003esslmode\u003c/code\u003e is changed to \u003ccode class=\"literal\"\u003everify-full\u003c/code\u003e, and any weaker setting will result in an error. In most cases it is trivial for anyone to obtain a certificate trusted by the system for a hostname they control, rendering \u003ccode class=\"literal\"\u003everify-ca\u003c/code\u003e and all weaker modes useless.\u003c/p\u003e\n\u003cp\u003eThe magic \u003ccode class=\"literal\"\u003esystem\u003c/code\u003e value will take precedence over a local certificate file with the same name. If for some reason you find yourself in this situation, use an alternative path like \u003ccode class=\"literal\"\u003esslrootcert=./system\u003c/code\u003e instead.\u003c/p\u003e\n\u003c/div\u003e\n\u003c/dd\u003e\u003c/dl\u003e\u003c/div\u003e","related":[{"label":"Connection service file","url":"/docs/18/libpq-pgservice.html"},{"label":"Password file","url":"/docs/18/libpq-pgpass.html"},{"label":"All libpq environment variables","url":"/docs/18/libpq-envars.html"}],"sections":[{"paragraphs":["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."],"title":"Default resolution and service-file precedence"},{"paragraphs":["PGSSLROOTCERT behaves the same as the sslrootcert connection parameter."],"title":"Environment variable evidence"}],"tables":[{"columns":[{"key":"name","label":"Variable"},{"key":"description","label":"Documented behavior"}],"key":"environment","rows":[{"description":"PGSSLROOTCERT behaves the same as the sslrootcert connection parameter.","name":{"text":"PGSSLROOTCERT","url":"/docs/18/libpq-envars.html"}}],"title":"Environment fallback"}]}},"RequestedLocale":"en","Fallback":false,"Versions":["10","11","12","13","14","15","16","17","18","19","20"],"Locales":["en","zh-Hans"],"Signatures":null,"Spellings":null,"SQLState":null,"Evidence":null}