{"Entry":{"collection":"conn","key":"password","name":"password","aliases":["PGPASSWORD","password"],"metadata":{"aliases":["PGPASSWORD","password"],"category":"Authentication","content_hash":"839ac586da75f166910d9c0b09944cb9cc3f85299281bca799ed6497a26ec4fa","derived_content_hash":"9c37904dd3a0c9ed78dca4151c50ddaf92fd6903d77c54f2446a51e3d7fc791b","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.026864+08:00","name":"password","name_zh":"","slug":"password","summary":"Password to be used if the server demands password authentication."}},"Definition":{"Collection":"conn","Key":"password","SourceDatabase":"center","Version":"18","SourceTable":"connection_parameter","SourceKey":"password","SourceRevision":"ee8d1a3612338fd9adf250730cb640fcc5233b5491337cc00a316a44e3a0b9f8","Facts":{"comparison_data":{"compiled_default_expression":"NULL","default_evidence":[],"definition":"Password to be used if the server demands password authentication.","documented":true,"environment":"PGPASSWORD","keyword":"password"},"comparison_hash":"af43ecc0f13e84b5df1356d44273d3110b1ed954a663efd39fc6da80ed8b3dfd","default_evidence":[],"description":["Password to be used if the server demands password authentication."],"description_zh":"服务器要求密码认证时所使用的密码。","description_zh_html":"\u003cp\u003e连接参数 password。\u003c/p\u003e\u003ch3\u003e同版本中文手册定义\u003c/h3\u003e\u003cdd\u003e\u003cp\u003e\n       服务器要求密码认证时所使用的密码。\n      \u003c/p\u003e\u003c/dd\u003e\u003cp\u003e\u003ca href=\"/zh/docs/18/libpq-connect.html#LIBPQ-CONNECT-PASSWORD\"\u003e查看完整中文手册与上下文\u003c/a\u003e。\u003c/p\u003e","documented":true,"environment":[{"description":"PGPASSWORD behaves the same as the password connection parameter. Use of this environment variable is not recommended for security reasons, as some operating systems allow non-root users to see process environment variables via ps ; instead consider using a password file (see Section 32.16 ).","name":"PGPASSWORD","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":"PGPASSWORD"},{"label":"Compiled fallback expression","value":"NULL"}],"facts_zh":[{"label":"客户端库","value":"libpq 18.6"},{"label":"手册定义","value":"手册已记载"},{"label":"源码中的环境变量回退","value":"PGPASSWORD"},{"label":"编译时回退表达式","value":"NULL"}],"keyword":"password","manual_html":"\u003cdiv\u003e\u003cdl class=\"variablelist\"\u003e\u003cdt id=\"LIBPQ-CONNECT-PASSWORD\"\u003e\u003cspan class=\"term\"\u003e\u003ccode class=\"literal\"\u003epassword\u003c/code\u003e\u003c/span\u003e \u003c/dt\u003e\u003cdd\u003e\n\u003cp\u003ePassword to be used if the server demands password authentication.\u003c/p\u003e\n\u003c/dd\u003e\u003c/dl\u003e\u003c/div\u003e\u003cdiv\u003e\u003cdiv class=\"sect1\" id=\"LIBPQ-PGPASS\"\u003e\n\u003cdiv class=\"titlepage\"\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e\n\u003ch2 class=\"title\"\u003e32.16. The Password File \u003c/h2\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003cp\u003eThe file \u003ccode class=\"filename\"\u003e.pgpass\u003c/code\u003e in a user's home directory can contain passwords to be used if the connection requires a password (and no password has been specified otherwise). On Unix systems, the directory can be specified by the \u003ccode class=\"envar\"\u003eHOME\u003c/code\u003e environment variable, or if undefined, the home directory of the effective user. On Microsoft Windows the file is named \u003ccode class=\"filename\"\u003e%APPDATA%\\postgresql\\pgpass.conf\u003c/code\u003e (where \u003ccode class=\"filename\"\u003e%APPDATA%\u003c/code\u003e refers to the Application Data subdirectory in the user's profile). Alternatively, the password file to use can be specified using the connection parameter \u003ca class=\"xref\" href=\"/docs/18/libpq-connect.html#LIBPQ-CONNECT-PASSFILE\"\u003epassfile\u003c/a\u003e or the environment variable \u003ccode class=\"envar\"\u003ePGPASSFILE\u003c/code\u003e.\u003c/p\u003e\n\u003cp\u003eThis file should contain lines of the following format:\u003c/p\u003e\n\u003cpre class=\"synopsis\"\u003e\u003cem class=\"replaceable\"\u003e\u003ccode\u003ehostname\u003c/code\u003e\u003c/em\u003e:\u003cem class=\"replaceable\"\u003e\u003ccode\u003eport\u003c/code\u003e\u003c/em\u003e:\u003cem class=\"replaceable\"\u003e\u003ccode\u003edatabase\u003c/code\u003e\u003c/em\u003e:\u003cem class=\"replaceable\"\u003e\u003ccode\u003eusername\u003c/code\u003e\u003c/em\u003e:\u003cem class=\"replaceable\"\u003e\u003ccode\u003epassword\u003c/code\u003e\u003c/em\u003e\n\u003c/pre\u003e\n\u003cp\u003e(You can add a reminder comment to the file by copying the line above and preceding it with \u003ccode class=\"literal\"\u003e#\u003c/code\u003e.) Each of the first four fields can be a literal value, or \u003ccode class=\"literal\"\u003e*\u003c/code\u003e, which matches anything. The password field from the first line that matches the current connection parameters will be used. (Therefore, put more-specific entries first when you are using wildcards.) If an entry needs to contain \u003ccode class=\"literal\"\u003e:\u003c/code\u003e or \u003ccode class=\"literal\"\u003e\\\u003c/code\u003e, escape this character with \u003ccode class=\"literal\"\u003e\\\u003c/code\u003e. The host name field is matched to the \u003ccode class=\"literal\"\u003ehost\u003c/code\u003e connection parameter if that is specified, otherwise to the \u003ccode class=\"literal\"\u003ehostaddr\u003c/code\u003e parameter if that is specified; if neither are given then the host name \u003ccode class=\"literal\"\u003elocalhost\u003c/code\u003e is searched for. The host name \u003ccode class=\"literal\"\u003elocalhost\u003c/code\u003e is also searched for when the connection is a Unix-domain socket connection and the \u003ccode class=\"literal\"\u003ehost\u003c/code\u003e parameter matches \u003cspan class=\"application\"\u003elibpq\u003c/span\u003e's default socket directory path. In a standby server, a database field of \u003ccode class=\"literal\"\u003ereplication\u003c/code\u003e matches streaming replication connections made to the primary server. The database field is of limited usefulness otherwise, because users have the same password for all databases in the same cluster.\u003c/p\u003e\n\u003cp\u003eOn Unix systems, the permissions on a password file must disallow any access to world or group; achieve this by a command such as \u003ccode class=\"command\"\u003echmod 0600 ~/.pgpass\u003c/code\u003e. If the permissions are less strict than this, the file will be ignored. On Microsoft Windows, it is assumed that the file is stored in a directory that is secure, so no special permissions check is made.\u003c/p\u003e\n\u003c/div\u003e\u003c/div\u003e","manual_path":"libpq-connect.html#LIBPQ-CONNECT-PASSWORD","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":["PGPASSWORD behaves the same as the password connection parameter. Use of this environment variable is not recommended for security reasons, as some operating systems allow non-root users to see process environment variables via ps ; instead consider using a password file (see Section 32.16 )."],"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":["PGPASSWORD 的行为与 password 连接参数相同。出于安全原因，不建议使用此环境变量，因为一些操作系统允许非root用户通过 ps 查看进程环境变量；而应考虑使用密码文件（参见 第 32.16 节 ）。"],"title":"环境变量证据"}],"signature":"password","source_option":{"compiled_default_expression":"NULL","declaration":"\"password\", \"PGPASSWORD\", NULL, NULL, \"Database-Password\", \"*\", 20, offsetof(struct pg_conn, pgpass)","environment":"PGPASSWORD","keyword":"password","source_notes":[]},"sources":[{"anchor":"LIBPQ-CONNECT-PASSWORD","file":"libpq-connect.html","label":"18.6 English manual · libpq-connect.html","sha256":"c26a7fc3dcda6066cfe540641ae2690faf3d3c03277f30b4dfc2328ab45c212f","url":"/docs/18/libpq-connect.html#LIBPQ-CONNECT-PASSWORD"},{"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"},{"anchor":"","file":"libpq-pgpass.html","label":"18.6 English manual · libpq-pgpass.html","sha256":"b926f6b6ae4e7d962b276438025b3d894c1442a69d861200c7d5b09be48f38d5","url":"/docs/18/libpq-pgpass.html"}],"tables":[{"columns":[{"key":"name","label":"Variable"},{"key":"description","label":"Documented behavior"}],"key":"environment","rows":[{"description":"PGPASSWORD behaves the same as the password connection parameter. Use of this environment variable is not recommended for security reasons, as some operating systems allow non-root users to see process environment variables via ps ; instead consider using a password file (see Section 32.16 ).","name":{"text":"PGPASSWORD","url":"/docs/18/libpq-envars.html"}}],"title":"Environment fallback"}],"tables_zh":[{"columns":[{"key":"name","label":"变量"},{"key":"description","label":"手册记载的行为"}],"key":"environment","rows":[{"description":"PGPASSWORD 的行为与 password 连接参数相同。出于安全原因，不建议使用此环境变量，因为一些操作系统允许非root用户通过 ps 查看进程环境变量；而应考虑使用密码文件（参见 第 32.16 节 ）。","name":{"text":"PGPASSWORD","url":"/docs/18/libpq-envars.html"}}],"title":"环境变量回退"}],"zh_from":{"authored_translation":"source-derived-identity","body_sha256":"e6e9e3140ab6d6c92a6ae8c602b00821a53c7d4b7271da2848236cc4a7b36cde","kind":"same-version-chinese-manual-with-source-derived-identity","manual":{"anchor":"LIBPQ-CONNECT-PASSWORD","build_id":107,"extraction":"exact-definition","fragment_sha256":"4ad982c35870ac50ae00b87f8e4ebae8674e26d9e7f2a30869172100cc03b73a","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-PASSWORD","version":"18"},"runtime_rerun":false,"source_facts_revision":"ee8d1a3612338fd9adf250730cb640fcc5233b5491337cc00a316a44e3a0b9f8"}},"ManualEvidence":{"manual_path":"libpq-connect.html#LIBPQ-CONNECT-PASSWORD","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-PASSWORD","file":"libpq-connect.html","label":"18.6 English manual · libpq-connect.html","sha256":"c26a7fc3dcda6066cfe540641ae2690faf3d3c03277f30b4dfc2328ab45c212f","url":"/docs/18/libpq-connect.html#LIBPQ-CONNECT-PASSWORD"},{"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"},{"anchor":"","file":"libpq-pgpass.html","label":"18.6 English manual · libpq-pgpass.html","sha256":"b926f6b6ae4e7d962b276438025b3d894c1442a69d861200c7d5b09be48f38d5","url":"/docs/18/libpq-pgpass.html"}]},"MeasuredEvidence":{}},"Text":{"Collection":"conn","Key":"password","SourceDatabase":"center","Version":"18","Locale":"en","Title":"password","Summary":"Password to be used if the server demands password authentication.","BodyHTML":"\u003cdiv\u003e\u003cdl\u003e\u003cdt id=\"LIBPQ-CONNECT-PASSWORD\"\u003e\u003cspan\u003e\u003ccode\u003epassword\u003c/code\u003e\u003c/span\u003e \u003c/dt\u003e\u003cdd\u003e\n\u003cp\u003ePassword to be used if the server demands password authentication.\u003c/p\u003e\n\u003c/dd\u003e\u003c/dl\u003e\u003c/div\u003e\u003cdiv\u003e\u003cdiv id=\"LIBPQ-PGPASS\"\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e\n\u003ch2\u003e32.16. The Password File \u003c/h2\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003cp\u003eThe file \u003ccode\u003e.pgpass\u003c/code\u003e in a user\u0026#39;s home directory can contain passwords to be used if the connection requires a password (and no password has been specified otherwise). On Unix systems, the directory can be specified by the \u003ccode\u003eHOME\u003c/code\u003e environment variable, or if undefined, the home directory of the effective user. On Microsoft Windows the file is named \u003ccode\u003e%APPDATA%\\postgresql\\pgpass.conf\u003c/code\u003e (where \u003ccode\u003e%APPDATA%\u003c/code\u003e refers to the Application Data subdirectory in the user\u0026#39;s profile). Alternatively, the password file to use can be specified using the connection parameter \u003ca href=\"/docs/18/libpq-connect.html#LIBPQ-CONNECT-PASSFILE\" rel=\"nofollow\"\u003epassfile\u003c/a\u003e or the environment variable \u003ccode\u003ePGPASSFILE\u003c/code\u003e.\u003c/p\u003e\n\u003cp\u003eThis file should contain lines of the following format:\u003c/p\u003e\n\u003cpre\u003e\u003cem\u003e\u003ccode\u003ehostname\u003c/code\u003e\u003c/em\u003e:\u003cem\u003e\u003ccode\u003eport\u003c/code\u003e\u003c/em\u003e:\u003cem\u003e\u003ccode\u003edatabase\u003c/code\u003e\u003c/em\u003e:\u003cem\u003e\u003ccode\u003eusername\u003c/code\u003e\u003c/em\u003e:\u003cem\u003e\u003ccode\u003epassword\u003c/code\u003e\u003c/em\u003e\n\u003c/pre\u003e\n\u003cp\u003e(You can add a reminder comment to the file by copying the line above and preceding it with \u003ccode\u003e#\u003c/code\u003e.) Each of the first four fields can be a literal value, or \u003ccode\u003e*\u003c/code\u003e, which matches anything. The password field from the first line that matches the current connection parameters will be used. (Therefore, put more-specific entries first when you are using wildcards.) If an entry needs to contain \u003ccode\u003e:\u003c/code\u003e or \u003ccode\u003e\\\u003c/code\u003e, escape this character with \u003ccode\u003e\\\u003c/code\u003e. The host name field is matched to the \u003ccode\u003ehost\u003c/code\u003e connection parameter if that is specified, otherwise to the \u003ccode\u003ehostaddr\u003c/code\u003e parameter if that is specified; if neither are given then the host name \u003ccode\u003elocalhost\u003c/code\u003e is searched for. The host name \u003ccode\u003elocalhost\u003c/code\u003e is also searched for when the connection is a Unix-domain socket connection and the \u003ccode\u003ehost\u003c/code\u003e parameter matches \u003cspan\u003elibpq\u003c/span\u003e\u0026#39;s default socket directory path. In a standby server, a database field of \u003ccode\u003ereplication\u003c/code\u003e matches streaming replication connections made to the primary server. The database field is of limited usefulness otherwise, because users have the same password for all databases in the same cluster.\u003c/p\u003e\n\u003cp\u003eOn Unix systems, the permissions on a password file must disallow any access to world or group; achieve this by a command such as \u003ccode\u003echmod 0600 ~/.pgpass\u003c/code\u003e. If the permissions are less strict than this, the file will be ignored. On Microsoft Windows, it is assumed that the file is stored in a directory that is secure, so no special permissions check is made.\u003c/p\u003e\n\u003c/div\u003e\u003c/div\u003e","SourceRevision":"ee8d1a3612338fd9adf250730cb640fcc5233b5491337cc00a316a44e3a0b9f8","ContentHash":"f860afc5acc6ab12139be4b42945487a16de080556468eb4543a28f27eb6d7ba","Payload":{"description":["Password to be used if the server demands password authentication."],"manual_html":"\u003cdiv\u003e\u003cdl class=\"variablelist\"\u003e\u003cdt id=\"LIBPQ-CONNECT-PASSWORD\"\u003e\u003cspan class=\"term\"\u003e\u003ccode class=\"literal\"\u003epassword\u003c/code\u003e\u003c/span\u003e \u003c/dt\u003e\u003cdd\u003e\n\u003cp\u003ePassword to be used if the server demands password authentication.\u003c/p\u003e\n\u003c/dd\u003e\u003c/dl\u003e\u003c/div\u003e\u003cdiv\u003e\u003cdiv class=\"sect1\" id=\"LIBPQ-PGPASS\"\u003e\n\u003cdiv class=\"titlepage\"\u003e\n\u003cdiv\u003e\n\u003cdiv\u003e\n\u003ch2 class=\"title\"\u003e32.16. The Password File \u003c/h2\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003c/div\u003e\n\u003cp\u003eThe file \u003ccode class=\"filename\"\u003e.pgpass\u003c/code\u003e in a user's home directory can contain passwords to be used if the connection requires a password (and no password has been specified otherwise). On Unix systems, the directory can be specified by the \u003ccode class=\"envar\"\u003eHOME\u003c/code\u003e environment variable, or if undefined, the home directory of the effective user. On Microsoft Windows the file is named \u003ccode class=\"filename\"\u003e%APPDATA%\\postgresql\\pgpass.conf\u003c/code\u003e (where \u003ccode class=\"filename\"\u003e%APPDATA%\u003c/code\u003e refers to the Application Data subdirectory in the user's profile). Alternatively, the password file to use can be specified using the connection parameter \u003ca class=\"xref\" href=\"/docs/18/libpq-connect.html#LIBPQ-CONNECT-PASSFILE\"\u003epassfile\u003c/a\u003e or the environment variable \u003ccode class=\"envar\"\u003ePGPASSFILE\u003c/code\u003e.\u003c/p\u003e\n\u003cp\u003eThis file should contain lines of the following format:\u003c/p\u003e\n\u003cpre class=\"synopsis\"\u003e\u003cem class=\"replaceable\"\u003e\u003ccode\u003ehostname\u003c/code\u003e\u003c/em\u003e:\u003cem class=\"replaceable\"\u003e\u003ccode\u003eport\u003c/code\u003e\u003c/em\u003e:\u003cem class=\"replaceable\"\u003e\u003ccode\u003edatabase\u003c/code\u003e\u003c/em\u003e:\u003cem class=\"replaceable\"\u003e\u003ccode\u003eusername\u003c/code\u003e\u003c/em\u003e:\u003cem class=\"replaceable\"\u003e\u003ccode\u003epassword\u003c/code\u003e\u003c/em\u003e\n\u003c/pre\u003e\n\u003cp\u003e(You can add a reminder comment to the file by copying the line above and preceding it with \u003ccode class=\"literal\"\u003e#\u003c/code\u003e.) Each of the first four fields can be a literal value, or \u003ccode class=\"literal\"\u003e*\u003c/code\u003e, which matches anything. The password field from the first line that matches the current connection parameters will be used. (Therefore, put more-specific entries first when you are using wildcards.) If an entry needs to contain \u003ccode class=\"literal\"\u003e:\u003c/code\u003e or \u003ccode class=\"literal\"\u003e\\\u003c/code\u003e, escape this character with \u003ccode class=\"literal\"\u003e\\\u003c/code\u003e. The host name field is matched to the \u003ccode class=\"literal\"\u003ehost\u003c/code\u003e connection parameter if that is specified, otherwise to the \u003ccode class=\"literal\"\u003ehostaddr\u003c/code\u003e parameter if that is specified; if neither are given then the host name \u003ccode class=\"literal\"\u003elocalhost\u003c/code\u003e is searched for. The host name \u003ccode class=\"literal\"\u003elocalhost\u003c/code\u003e is also searched for when the connection is a Unix-domain socket connection and the \u003ccode class=\"literal\"\u003ehost\u003c/code\u003e parameter matches \u003cspan class=\"application\"\u003elibpq\u003c/span\u003e's default socket directory path. In a standby server, a database field of \u003ccode class=\"literal\"\u003ereplication\u003c/code\u003e matches streaming replication connections made to the primary server. The database field is of limited usefulness otherwise, because users have the same password for all databases in the same cluster.\u003c/p\u003e\n\u003cp\u003eOn Unix systems, the permissions on a password file must disallow any access to world or group; achieve this by a command such as \u003ccode class=\"command\"\u003echmod 0600 ~/.pgpass\u003c/code\u003e. If the permissions are less strict than this, the file will be ignored. On Microsoft Windows, it is assumed that the file is stored in a directory that is secure, so no special permissions check is made.\u003c/p\u003e\n\u003c/div\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":["PGPASSWORD behaves the same as the password connection parameter. Use of this environment variable is not recommended for security reasons, as some operating systems allow non-root users to see process environment variables via ps ; instead consider using a password file (see Section 32.16 )."],"title":"Environment variable evidence"}],"tables":[{"columns":[{"key":"name","label":"Variable"},{"key":"description","label":"Documented behavior"}],"key":"environment","rows":[{"description":"PGPASSWORD behaves the same as the password connection parameter. Use of this environment variable is not recommended for security reasons, as some operating systems allow non-root users to see process environment variables via ps ; instead consider using a password file (see Section 32.16 ).","name":{"text":"PGPASSWORD","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}