尝试使用PG转储,但密码不起作用

发布于 2025-01-22 06:29:22 字数 601 浏览 4 评论 0原文

我一直在尝试使用pg_dump,但我一直在遇到错误:

C:\Users\ojadi>pg_dump
Password:
pg_dump: error: connection to server at "localhost" (::1), port 5432 failed: FATAL:  password authentication failed for user "ojadi"

我尝试从中更改PG_HBA文件

to

我一直在搜索但没有工作,我是否缺少一些东西

I've been trying to use pg_dump but I keep getting the error:

C:\Users\ojadi>pg_dump
Password:
pg_dump: error: connection to server at "localhost" (::1), port 5432 failed: FATAL:  password authentication failed for user "ojadi"

I've tried changing the pg_hba file from
enter image description here

To
enter image description here

I've been searching but nothings working, am I missing something

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

〃安静 2025-01-29 06:29:22

pg_hba.conf文件是顺序读取的,您的条目已找到并且结束时,请在开始时添加您的条目​​,不要忘记运行重新加载

文档: https://www.postgresql.org.org.org/docs/docs/current/current/current/auth-pgg-hba -conf.html

由于pg_hba.conf记录对每次连接尝试都进行了顺序检查,因此记录的顺序很重要。通常,较早的记录将具有紧密的连接匹配参数和较弱的身份验证方法,而后来的记录将具有更宽松的匹配参数和更强的身份验证方法。

The pg_hba.conf file is read sequentially, and your entries are located and the end, please add your entries at the beginning, and don't forget to run a reload

The doc: https://www.postgresql.org/docs/current/auth-pg-hba-conf.html

Since the pg_hba.conf records are examined sequentially for each connection attempt, the order of the records is significant. Typically, earlier records will have tight connection match parameters and weaker authentication methods, while later records will have looser match parameters and stronger authentication methods.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文