blocks|key|331307|text|您的应用程序使用与PostgreSQL客户端C库libpq链接的API。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|331308|该库的版本必须是9.6或更高版本，并且在v10中引入了SCRAM身份验证。|331309|在应用程序结束libpq+上升级，然后重试。|BOLD|331310|如果不需要scram-sha-256身份验证，则可以恢复为md5|331311|在password_encryption+=+md5中设置postgresql.conf|unordered-list-item|331312|在md5中将身份验证方法更改为pg_hba.conf|331313|重装PostgreSQL|331314|更改用户密码以获得MD5加密密码|331315|entityMap^0|O|5|0|0|7|5|D|3|0|5|D|T|3|0|1|P|T|F|0|1|3|F|B|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|J]]|D|@]|E|$]]|$1|K|3|L|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|M|3|N|5|O|7|1B|8|@$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|O|7|1G|8|@$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|R|3|S|5|O|7|1L|8|@]|D|@]|E|$]]|$1|T|3|U|5|O|7|1M|8|@]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1N|8|@]|D|@]|E|$]]]|W|$]]

Your application uses an API that is linked with the PostgreSQL client C library <code>libpq</code>.
The version of that library must be 9.6 or older, and SCRAM authentication was introduced in v10.
Upgrade <code>libpq</code> on the application end and try again.
If you don't need <code>scram-sha-256</code> authentication, you can revert to <code>md5</code>:
<ul>
<li>set <code>password_encryption = md5</code> in <code>postgresql.conf</code></li>
<li>change the authentication method to <code>md5</code> in <code>pg_hba.conf</code></li>
<li>reload PostgreSQL</li>
<li>change the password of the user to get an MD5 encrypted password</li>
</ul>

blocks|key|391710|text|遇到了同样的问题，并应用了@Laurenz的修复程序，但是由于加密策略的改变，我会在我的用户上得到一个数据库的身份验证错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|391711|因此，与其将scram-sha-256替换为md5，不如在pg_hba.conf中用trust替换它|offset|length|style|CODE|391712|entityMap^0|0|6|D|M|3|T|B|16|5|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]|$D|P|E|Q|F|G]|$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|I|$]]

Encountered the same issue and applied @Laurenz Albe's fix but I would get an authentication error on my user for the database, because of encryption strategy change.
So instead of replacing <code>scram-sha-256</code> with <code>md5</code>, replace it with <code>trust</code> in <code>pg_hba.conf</code>

blocks|key|395185|text|我以前在中运行php+artisan+migrate时，需要libpq+10或更高版本的身份验证时会出现错误。然后，我将其修正如下:将身份验证从scram-sha-256更改为md5，然后是reset+your+password和restart+the+postgresql-x64-13+service，下面是逐步进行的：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|395186|步骤1：在C:\Program+Files\PostgreSQL\13\data中查找文件postgresql.conf，然后设置password_encryption+=+md5|ordered-list-item|395187|步骤2：在C:\Program+Files\PostgreSQL\13\data中查找文件pg_hba.conf，然后将所有METHOD更改为md5|395188|步骤3：打开command+line+(cmd,cmder,git+bash...)并运行psql+-U+postgres，然后在安装postgres时输入密码|395189|步骤4:然后在命令行中运行ALTER+USER+postgres+WITH+PASSWORD+'new-password'更改密码|395190|Final:在您的postgresql-x64-13中重新启动服务Service。|395191|entityMap^0|4|14|7|J|20|D|2G|3|2N|J|37|11|0|0|3|5|Z|19|F|1T|P|0|0|3|5|Z|19|B|1Q|6|1Z|3|0|0|3|6|10|19|G|0|D|1C|0|9|H|X|7|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|D]|$9|Y|A|Z|B|D]|$9|10|A|11|B|D]|$9|12|A|13|B|D]|$9|14|A|15|B|D]]|E|@]|F|$]]|$1|G|3|H|5|I|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|D]|$9|1B|A|1C|B|D]|$9|1D|A|1E|B|D]]|E|@]|F|$]]|$1|J|3|K|5|I|7|1F|8|@$9|1G|A|1H|B|C]|$9|1I|A|1J|B|D]|$9|1K|A|1L|B|D]|$9|1M|A|1N|B|D]|$9|1O|A|1P|B|D]]|E|@]|F|$]]|$1|L|3|M|5|I|7|1Q|8|@$9|1R|A|1S|B|C]|$9|1T|A|1U|B|D]|$9|1V|A|1W|B|D]]|E|@]|F|$]]|$1|N|3|O|5|I|7|1X|8|@$9|1Y|A|1Z|B|D]]|E|@]|F|$]]|$1|P|3|Q|5|I|7|20|8|@$9|21|A|22|B|D]|$9|23|A|24|B|D]]|E|@]|F|$]]|$1|R|3|-4|5|6|7|25|8|@]|E|@]|F|$]]]|S|$]]

I used to get an error SCRAM authentication requires libpq version 10 or above when running <code>php artisan migrate</code> in <code>laravel 8</code>. Then I fixed it as follows: Change authentication from <code>scram-sha-256</code> to <code>md5</code>, then <code>reset your password</code> and <code>restart the postgresql-x64-13 service</code> and here are step by step:
<ol>
<li>Step 1: Find file <code>postgresql.conf</code> in <code>C:\Program Files\PostgreSQL\13\data</code> then set <code>password_encryption = md5</code></li>
<li>Step 2: Find file <code>pg_hba.conf</code> in <code>C:\Program Files\PostgreSQL\13\data</code> then change all <code>METHOD</code> to <code>md5</code></li>
<li>Step 3: Open <code>command line (cmd,cmder,git bash...)</code> and run <code>psql -U postgres</code> then enter your password when installed postgres sql</li>
<li>Step 4: Then change your password by run <code>ALTER USER postgres WITH PASSWORD 'new-password'</code> in command line</li>
<li>Final: Restart service <code>postgresql-x64-13</code> in your <code>Service</code>.</li>
</ol>

blocks|key|391734|text|如果你想保持安全的话。您需要更新客户端postgreSQL库，因为php-pgsql默认版本不支持它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|391735|CentOS/Rhel/Rocky|BOLD|391736|yum+install+https://download.postgresql.org/pub/repos/yum/reporpms/EL-7-x86_64/pgdg-redhat-repo-latest.noarch.rpm
yum+install+postgresql13|code-block|syntax|javascript|391737|这将更新服务器/客户端libpq，以便继续使用scram-sha-256。|391738|entityMap^0|X|9|0|0|H|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|H]]|D|@]|E|$]]|$1|I|3|J|5|K|7|X|8|@]|D|@]|E|$L|M]]|$1|N|3|O|5|6|7|Y|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|Q|$]]

If you want to keep the scram-sha-256 for security. You need to update your client postgreSQL libraries, due to <code>php-pgsql</code> default version does not support it.
CentOS/Rhel/Rocky
<pre><code>yum install https://download.postgresql.org/pub/repos/yum/reporpms/EL-7-x86_64/pgdg-redhat-repo-latest.noarch.rpm
yum install postgresql13
</code></pre>
This will update the server/client libpq in order to keep using scram-sha-256

blocks|key|331352|text|RUN+apt-get+-y+update+\
++++&&+apt-get+install+-y+build-essential+gettext+libpq-dev\
++++&&+apt-get+install+-y+wkhtmltopdf\
++++&&+apt-get+install+-y+gdal-bin\
++++&&+apt-get+install+-y+libgdal-dev\
++++&&+apt-get+install+-y+--no-install-recommends+software-properties-common\
++++&&+apt-add-repository+contrib\
++++&&+apt-get+update|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|331353|尝尝这个。|unstyled|331354|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>RUN apt-get -y update \
 &amp;&amp; apt-get install -y build-essential gettext libpq-dev\
 &amp;&amp; apt-get install -y wkhtmltopdf\
 &amp;&amp; apt-get install -y gdal-bin\
 &amp;&amp; apt-get install -y libgdal-dev\
 &amp;&amp; apt-get install -y --no-install-recommends software-properties-common\
 &amp;&amp; apt-add-repository contrib\
 &amp;&amp; apt-get update
</code></pre>
Try this.

blocks|key|331362|text|对于那些基于m1的macs上的人来说，他们目前在坞中看到了这个问题--在libpg的上游出现了一个bug，这是针对ARM上错误的库版本构建的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|331363|在修复之前，解决方法是(在性能测试中)只使用通过罗塞塔。|offset|length|331364|export+DOCKER_DEFAULT_PLATFORM=linux/amd64，并重建你的图像。|style|CODE|331365|您将得到libpq的最新版本，并且一切都应该正常工作。|331366|参考文献：https://github.com/psycopg/psycopg2/issues/1360|331367|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.docker.com/desktop/mac/apple-silicon/|1|https://github.com/psycopg/psycopg2/issues/1360^0|0|M|5|0|0|0|16|0|0|5|1B|1|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]]|A|$]]|$1|F|3|G|5|6|7|12|8|@$D|13|E|14|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|15|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|16|8|@]|9|@$D|17|E|18|1|19]]|A|$]]|$1|N|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]|V|$5|Q|R|S|A|$T|W]]]]

For those on M1-Based macs who are currently seeing this issue in docker - there appears to a bug upstream in libpg that's building against the wrong library version on ARM.
Until it's fixed, a workaround is to (at a performance hit) is to just <a href="https://docs.docker.com/desktop/mac/apple-silicon/" rel="noreferrer">run it via rosetta</a>.
<code>export DOCKER_DEFAULT_PLATFORM=linux/amd64</code>, and re-build your images.
You'll get the latest version of libpq, and things should Just Work.
Ref: <a href="https://github.com/psycopg/psycopg2/issues/1360" rel="noreferrer">https://github.com/psycopg/psycopg2/issues/1360</a>

blocks|key|331380|text|我在运行安装了python:3.9的psycopg2-binary==2.9.3的psycopg2-binary==2.9.3映像时遇到了这个问题。安装psycopg2==2.9.3反而为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|331381|entityMap^0|7|A|I|M|15|M|24|F|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|G|$]]

I ran into this while running a <code>python:3.9</code> docker image where I had installed <code>psycopg2-binary==2.9.3</code>. Installing <code>psycopg2==2.9.3</code> instead resolved it for me.

blocks|key|395216|text|对于Amazone+linux用户：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|395217|$+sudo+yum+install+-y+amazon-linux-extras|code-block|syntax|javascript|395218|然后重新安装postgres客户端|395219|$+sudo+amazon-linux-extras+install+postgresql10|395220|然后主要部分安装python包--在我的例子中--是(psycopg2)重新安装它|395221|$+pip3+install+--force-reinstall+psycopg2==2.93|395222|规格:+python3.8.9|395223|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

For Amazone linux users:
<pre><code>$ sudo yum install -y amazon-linux-extras
</code></pre>
then re install the postgres client again
<pre><code>$ sudo amazon-linux-extras install postgresql10
</code></pre>
Then the main part install the python package in my case it was (psycopg2) reinstall it
<pre><code>$ pip3 install --force-reinstall psycopg2==2.93
</code></pre>
specification:
python3.8.9

blocks|key|331457|text|有此问题，并通过从二进制版本的psycopg2切换到psycopg2+=+"%5E2.9.3"来修复它。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|331458|entityMap^0|F|8|Q|J|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Had this issue and fixed it by switching from the binary version of <code>psycopg2</code> to <code>psycopg2 = &quot;^2.9.3&quot;</code>

blocks|key|391820|text|我找到了两个解决方案。我没有尝试当地的，解决方案是码头集装箱。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|391821|初步信息:根据我们在Dockerfile开头定义的主图像，我们的libq版本可能有所不同。在给出的这里的答案中用例子说明了这一点。|offset|length|391822|如果您想知道您在坞映像中使用的libq版本，可以分别执行以下操作。|391823|船坞后-合成运行
docker-compose+exec+<app_name_in_docker-compose_file>+sh
python
import+psycopg2
print(psycopg2.extensions.libpq_version())|unordered-list-item|style|CODE|391824|如果您收到错误，您可能会在这里看到一个类似于90xxx的数字。|391825|解决办法：|391826|第一个基本的。我在码头上用了‘python:3.9-slim+buster’，我犯了错误。将基本图像名称更改为“python:3.9.6-al菠萝3.14”|391827|第二个解决方案是构建psycopg2文件并安装libq和其他依赖项。为此，将以下命令添加到dockerfile中。|391828|运行apt+update+-y+&&+apt安装-y构建-基本的libpq-dev运行pip3安装心理pip3+2-二进制-非二进制内核pip3+2-二进制|blockquote|391829|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/70167233/11681124|1|https://stackoverflow.com/a/70578039/11681124^0|0|1D|2|0|0|0|9|1K|1U|6|21|F|2H|16|0|0|0|0|Y|2|1|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|18|8|@]|9|@$D|19|E|1A|1|1B]]|A|$]]|$1|F|3|G|5|6|7|1C|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|1D|8|@$D|1E|E|1F|K|L]|$D|1G|E|1H|K|L]|$D|1I|E|1J|K|L]|$D|1K|E|1L|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1M|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1N|8|@]|9|@]|A|$]]|$1|Q|3|R|5|J|7|1O|8|@]|9|@]|A|$]]|$1|S|3|T|5|J|7|1P|8|@]|9|@$D|1Q|E|1R|1|1S]]|A|$]]|$1|U|3|V|5|W|7|1T|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]]|Y|$Z|$5|10|11|12|A|$13|14]]|15|$5|10|11|12|A|$13|16]]]]

I find 2 solutions. I didn't try local, solutions are for docker container.
Preliminary information:
According to the main image we defined at the beginning of the Dockerfile, our libq versions may differ. It is explained with examples in the answer given <a href="https://stackoverflow.com/a/70167233/11681124">here</a>.
If you want to know your libq version used in your docker-image, you can do the following, respectively.
<ul>
<li>After docker-compose run
<code>docker-compose exec &lt;app_name_in_docker-compose_file&gt; sh</code>
<code>python</code>
<code>import psycopg2</code>
<code>print(psycopg2.extensions.libpq_version())</code>
</li>
</ul>
If you're getting an error, you'll probably see a number like 90xxx here.
Solutions:
<ul>
<li>First basic one. I used 'python:3.9-slim-buster' at docker and I've got error. Change base image name to 'python:3.9.6-alpine3.14'</li>
<li>The second solution is to build the psycopg2 file and install libq and other dependencies. <a href="https://stackoverflow.com/a/70578039/11681124">For this</a>, add the following commands to the dockerfile.</li>
</ul>
<blockquote>
RUN apt update -y &amp;&amp; apt install -y build-essential libpq-dev
</blockquote>
<blockquote>
RUN pip3 install psycopg2-binary --no-binary psycopg2-binary
</blockquote>

blocks|key|1278676|text|所有建议将密码加密恢复到md5的答案都忘记了，出于安全原因，PostgreSQL将其默认密码加密从md5更改为scram-sha-256。因此，问题在于那些未能使用这种现代加密方法的客户机应用程序。随libpq版本10和更高版本一起提供的PostgreSQL文件很好。如果可以，只需更改客户端应用程序，以便只使用支持此新方法的应用程序。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1278677|例如，很长一段时间以来，我一直在使用一个名为RPostgreSQL的包，该包允许用户从R连接到PostgreSQL数据库。原来这个包不支持scram-sha-256。我现在已经用它的现代同义词rpostgres代替了它。问题解决了，大家都高兴了！|1278678|entityMap^0|C|3|1D|3|1J|D|2S|5|0|M|B|17|1|1X|D|2O|9|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|I|$]]

All the answers that are suggesting that password encryption should be reverted back to <code>md5</code> are forgetting that PostgreSQL changed its default password encryption from <code>md5</code> to <code>scram-sha-256</code> for security reasons.
The issue then is those client applications that fail to use this modern encryption method. The <code>libpq</code> file that ships with PostgreSQL version 10 and above is fine. Just change your client applications if you can so that you use only the ones that support this new method.
For instance, For a long time I was using a package called <code>RPostgreSQL</code> that allows users to connect to a PostgreSQL database from <code>R</code>. Turns out that package doesn't support <code>scram-sha-256</code>. I have now replaced it with its modern equivalent called <code>rpostgres</code>. Problem solved, everybody happy now!

blocks|key|331549|text|此问题仍然影响运行python:3.10.*停靠容器的python:3.10.*+macs+(基于aarch64+Debian+11)。对我来说，解决方案是安装psycopg2+(从源代码构建)，而不是psycopg2-binary，这是为生产提供建议的：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|331550|pip+install+psycopg2|code-block|syntax|javascript|331551|python容器已经拥有所有的构建依赖项(比如gcc)。一个更适合生产的容器很可能不会有这些https://www.psycopg.org/docs/install.html#build-prerequisites|331552|entityMap|0|LINK|mutability|MUTABLE|url|https://www.psycopg.org/docs/install.html#build-prerequisites^0|9|D|R|D|28|8|2T|F|0|0|1A|1P|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]|$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|14|8|@]|D|@$9|15|A|16|1|17]]|E|$]]|$1|M|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

This issue still affects m1 macs running <code>python:3.10.*</code> docker containers (based off aarch64 Debian 11). Solution for me was to install <code>psycopg2</code> (build from source) instead of <code>psycopg2-binary</code> which is advised for production anyways:
<pre><code>pip install psycopg2
</code></pre>
The python container has all the build dependencies already (like gcc). A more production appropriate container most likely won't have these <a href="https://www.psycopg.org/docs/install.html#build-prerequisites" rel="nofollow noreferrer">https://www.psycopg.org/docs/install.html#build-prerequisites</a>

blocks|key|391901|text|这是一个更平凡的答案，但这就是我身上发生的事情，所以我要在这里补充一下。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|391902|当我试图启动PostgreSQL+9.4时，我得到了这个错误。我意识到我已经在运行PostgreSQL+11+--它是从我的电脑自动启动的。一旦我停止了version+11，我就能够启动9.4版本。它们无法在已经使用的端口上侦听，而且都具有相同的端口集。但我不太清楚为什么会有误导性错误的措辞。|391903|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Here is a more mundane answer, but this is what happened to me so I'll add it here.
I got this error when I tried to start PostgreSQL 9.4. I realized I already had PostgreSQL 11 running - it started automatically with my computer. Once I stopped version 11, I was able to start version 9.4. They can't listen on a port already in use, and both had the same port set. But I'm not sure exactly why the misleading error wording.

blocks|key|1278802|text|在Mac+M1上安装python3.10的ubuntu22.04映像上发现了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1278803|对我起作用的是将psycopg2包安装为根程序包，而不是使用--user+--然后特定的用户可以使用该包。|offset|length|style|CODE|1278804|看起来，--user安装将一个链接错误的libpq放在/home/<user...>/.local/lib/python3.10/site-packages/psycopg2_binary.libs/libpq-d97d8807.so.5.9上。|1278805|如果在此之后启动了另一个pip+install+--user进程，并且在.local路径下再次安装psycopg2，只需将其从.local/lib/python3.x/site-packages/psycopg2*中删除即可。|1278806|entityMap^0|0|U|6|0|4|6|R|2M|0|C|I|10|6|1R|18|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@$D|S|E|T|F|G]|$D|U|E|V|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@$D|X|E|Y|F|G]|$D|Z|E|10|F|G]|$D|11|E|12|F|G]]|9|@]|A|$]]|$1|L|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|M|$]]

Found this problem installing on a ubuntu 22.04 image with python3.10 on Mac M1. 
What worked for me was installing the psycopg2 package as root rather than with <code>--user</code> - then the specific user can use the package.
Looks like the <code>--user</code> install puts an incorrectly linked libpq at
<code>/home/&lt;user...&gt;/.local/lib/python3.10/site-packages/psycopg2_binary.libs/libpq-d97d8807.so.5.9</code>
If you have another <code>pip install --user</code> process kicking about after this, and it installs psycopg2 again under the <code>.local</code> path, just remove that from <code>.local/lib/python3.x/site-packages/psycopg2*</code>

I am getting an error after moving the project to production. The error is as follows while running with production server
pg_connect(): Unable to connect to PostgreSQL server: SCRAM authentication requires libpq version 10 or above.
Here is my postgreSQL version:
Development Version :
PostgreSQL 11.5 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623
(Red Hat 4.8.5-36), 64-bit
Production Version :
PostgreSQL 11.5 (EnterpriseDB Advanced Server 11.5.12) on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36), 64-bit

How can I solve Postgresql SCRAM authentication problem?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在将项目转移到生产中后，我得到了一个错误。在生产服务器上运行时，错误如下pg_connect()：无法连接到PostgreSQL服务器: SCRAM身份验证需要libpq版本10或更高版本.这是我的postgreSQL版本：开发版本:PostgreSQL 11.5在x86_64-pc-linux-gnu上，由gcc (...

问如何解决Postgresql身份验证问题？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何解决Postgresql身份验证问题？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何解决Postgresql身份验证问题？
EN