blocks|key|367953|text|邮政局长是PostgreSQL的主要进程。您正在尝试启动已经在运行的PostgreSQL+(您自己说您可以连接到它)。跳过这一步就行了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|367954|entityMap|0|LINK|mutability|MUTABLE|url|http://www.postgresql.org/docs/9.5/static/app-postmaster.html^0|0|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

<a href="http://www.postgresql.org/docs/9.5/static/app-postmaster.html" rel="noreferrer">Postmaster</a> is the main PostgreSQL process. You're trying to start PostgreSQL that's already running (and you're saying yourself you can connect to it). Just skip that step of your process.

blocks|key|1123457|text|因为您可以连接到数据库，所以不需要再次启动服务器--它已经在运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1123458|pg_ctl用于控制PostgreSQL服务器。由于您的服务器已经启动，您的命令：|offset|length|style|CODE|1123459|pg_ctl+-D+/usr/local/var/postgres+start|code-block|syntax|javascript|1123460|返回一个错误，说明postmaster.pid上有一个锁--这是正确的，因为已经有一个服务器运行在该PID之下。|1123461|有两种方式：|1123462|最基本的方法--跳过这个步骤，您的服务器已经在运行了！|ordered-list-item|BOLD|1123463|执行一个不必要的操作-停止服务器，然后再启动它。|1123464|您可以停止服务器执行以下操作：|1123465|pg_ctl+-D+/usr/local/var/postgres+stop|1123466|这样，您就不再有邮政局长的锁，您可以使用您的命令来重新启动它。|1123467|entityMap|0|LINK|mutability|MUTABLE|url|https://www.postgresql.org/docs/current/static/app-pg-ctl.html^0|0|0|6|0|6|0|0|0|9|E|0|0|8|H|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@$D|1C|E|1D|F|G]]|9|@$D|1E|E|1F|1|1G]]|A|$]]|$1|H|3|I|5|J|7|1H|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1I|8|@$D|1J|E|1K|F|G]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1L|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|1M|8|@$D|1N|E|1O|F|T]]|9|@]|A|$]]|$1|U|3|V|5|S|7|1P|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|J|7|1R|8|@]|9|@]|A|$K|L]]|$1|10|3|11|5|6|7|1S|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]]]

Since you can connect to the database, you don't need to start the server again - it's already running.

<hr>

<a href="https://www.postgresql.org/docs/current/static/app-pg-ctl.html" rel="nofollow noreferrer"><code>pg_ctl</code></a> is used to control the PostgreSQL server. Since your server is already started, your command:

<pre><code>pg_ctl -D /usr/local/var/postgres start
</code></pre>

Returns an error, saying that there is a lock on <code>postmaster.pid</code> - which is true since there is already a server running under that PID.

<hr>

There are two ways:

<ol>
<li>The most basic way - skip that step, your server is already running!</li>
<li>Executing a needless operation - stopping the server, and then starting it again.</li>
</ol>

You could stop your server doing :

<pre><code>pg_ctl -D /usr/local/var/postgres stop
</code></pre>

So that you won't have the lock on postmaster anymore and you could use your command to start it again.

blocks|key|592111|text|如果它对其他人有帮助，请张贴此信息：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|592112|当我的笔记本电脑坏掉的时候，我在重新启动后遇到了和OP一样的问题。帮助我的是运行以下命令来查看与postmaster.pid关联的PID：|592113|cat+/usr/local/var/postgres/postmaster.pid|code-block|syntax|javascript|592114|出现的第一个数字是PID。在Activity中，我能够看到Postgres正在运行，但是没有一个与显示的PID数字相匹配的PID数字。|592115|与在超级用户上引用的答案中列出的步骤不同，我正确地重新启动了我的笔记本，然后打开终端并运行|592116|brew+services+restart+postgresql|592117|这在不需要删除postmaster.pid的情况下有效，我看到了其他几篇文章推荐的内容。有时候，简单的解决方案才能奏效。|592118|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|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|X|8|@]|9|@]|A|$G|H]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Posting this in case it helps someone else: 

I was having this same problem as the OP after a hard reboot when my laptop crashed. What helped me was running the following command to see what PID was associated with postmaster.pid: 

<pre><code>cat /usr/local/var/postgres/postmaster.pid
</code></pre>

The first number that appears will be the PID. Looking in Activity Monitor, I was able to see that Postgres was running, but without a PID number that matched the one shown. 

Instead of the steps outlined in the answer referenced on Superuser, I restarted my laptop properly and then opened up Terminal and ran 

<pre><code>brew services restart postgresql
</code></pre>

This worked without having to remove postmaster.pid, which I saw a few other posts recommend. Sometimes it's the simple solutions that work.

blocks|key|1123517|text|当我的系统意外关闭时，我经常在OSx中发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1123518|您只需删除文件postmaster.pid即可。|offset|length|style|CODE|1123519|cd+Library/Application+Support/Postgres/var-{postgres-version}|code-block|syntax|javascript|1123520|并删除postmaster.pid文件|1123521|如果您使用brew，那么您的路径应该如下所示：|1123522|/usr/local/var/postgres/postmaster.pid|1123523|使用以下命令重新启动Postgres|1123524|pg_ctl+-D+/usr/local/var/postgres+restart|1123525|entityMap^0|0|7|E|0|0|0|5|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@$D|10|E|11|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|12|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|13|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|14|8|@$D|15|E|16|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|J|7|17|8|@]|9|@]|A|$K|L]]|$1|S|3|T|5|6|7|18|8|@]|9|@]|A|$]]|$1|U|3|V|5|J|7|19|8|@]|9|@]|A|$K|L]]|$1|W|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|X|$]]

It often happens to me in OSx, when my system shutdown unexpectedly.
You can just remove the file <code>postmaster.pid</code>.
<pre><code>cd Library/Application Support/Postgres/var-{postgres-version}
</code></pre>
and remove the postmaster.pid file
in case you use <code>brew</code> then your path should be something like:
<pre><code>/usr/local/var/postgres/postmaster.pid
</code></pre>
restart the Postgres by using this command
<pre><code>pg_ctl -D /usr/local/var/postgres restart
</code></pre>

blocks|key|368128|text|我的OSX笔记本电脑突然关机，我在PostgresApp中得到了一个陈旧的PostgresApp错误。关闭我的笔记本电脑，并再次打开它解决了问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|368129|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

My OSX laptop had shutdown unexpectedly, and I was getting a stale postmaster.pid error in the PostgresApp. Shutting down my laptop and turning it back on again solved the problem.

blocks|key|1123560|text|如果您已经用brew安装了postgres，那么只需运行以下命令，它将管理所有东西|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1123561|+brew+services+restart+postgresql|code-block|syntax|javascript|1123562|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If you have installed postgres with brew then simply run the following command and it will manage everything

<pre><code> brew services restart postgresql
</code></pre>

blocks|key|589737|text|如果你没有重要的数据可以丢失：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|589738|sudo+killAll+postgres
brew+services+restart+postgresql|code-block|syntax|javascript|589739|再次:您可以通过这样做来破坏数据！|589740|冒着自己的风险去做吧！|589741|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

If you got no important data to lose :
<pre><code>sudo killAll postgres
brew services restart postgresql
</code></pre>
AGAIN : You could get data corrupted by doing this !
do it at your own risk !

blocks|key|368170|text|我正在使用mac，这些步骤对我来说很有用：-|type|unstyled|depth|inlineStyleRanges|entityRanges|data|368171|step1:+cd库/应用程序\支持/+Postgres+(最常见的是您的Postgres安装将位于这里)|368172|step2:+cd+13(如果您使用的是版本12，那么使用cd+12。希望得到了重点)|368173|step3:+ls+(正如您在发现postmaster.pid的文件中所看到的那样，完美)。|368174|step4:+rm+postmaster.pid|368175|删除陈旧的postmaster.pid文件后，可以重新启动PostgreSQL，一切都应该正常工作。|368176|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

I am using mac and these step work for me:-
step1: cd Library/Application\ Support/Postgres
(most commonly your Postgres installation will be located here)
step2: cd var-13
(if you are using version 12 then use cd var-12. Hope got the point)
step3: ls
(As you can see among the files you find the postmaster.pid, perfect.)
step4: rm postmaster.pid
When you have removed the stale postmaster.pid file you can restart PostgreSQL and everything should work as normal.

blocks|key|1123629|text|当系统意外关闭时，我的postgres崩溃，我无法连接到它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1123630|对我有用的是：|1123631|1˚检查postgres日志：|1123632|tail+-n+10000+/usr/local/var/log/postgres.log|code-block|syntax|javascript|1123633|2˚找到后置的PID，应该如下所示：|1123634|FATAL:++lock+file+"postmaster.pid"+already+exists
HINT:+++Is+another+postmaster+(PID+707)+running+in+data+directory+"/usr/local/var/postgres"?|1123635|3˚杀死这一过程：|1123636|kill+707|1123637|4˚重新启动postgres|1123638|brew+services+restart+postgresql|1123639|在这些步骤之后，我能够连接到rails应用程序中的数据库。|1123640|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|13|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|14|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|15|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|R|5|H|7|17|8|@]|9|@]|A|$I|J]]|$1|S|3|T|5|6|7|18|8|@]|9|@]|A|$]]|$1|U|3|V|5|H|7|19|8|@]|9|@]|A|$I|J]]|$1|W|3|X|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|Z|$]]

When the system shutdown unexpectedly, my postgres crashs and i'm unable to connect to it.
What worked for me was:
1˚ Check postgres log:
<pre><code>tail -n 10000 /usr/local/var/log/postgres.log
</code></pre>
2˚ Find the PID of postgress, should look like this:
<pre><code>FATAL: lock file &quot;postmaster.pid&quot; already exists
HINT: Is another postmaster (PID 707) running in data directory &quot;/usr/local/var/postgres&quot;?
</code></pre>
3˚ Kill that process:
<pre><code>kill 707
</code></pre>
4˚ Restart your postgres
<pre><code>brew services restart postgresql
</code></pre>
After those steps i was able to connect to the database within my rails application.

blocks|key|368229|text|经过很长一段时间的搜索，我在这里补充了一些对我有用的东西：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|368230|删除postmaster.pid文件：
rm+/usr/local/var/postgres/postmaster.pid|ordered-list-item|offset|length|style|CODE|368231|重新启动postgres：
brew+services+restart+postgresql|368232|希望这能帮到某人..。|368233|更新8/2022：|368234|正如迈克所评论的，对于M1+Mac，您可以将第1阶段替换为：|368235|rm+/opt/homebrew/var/postgresql/postmaster.pid|code-block|syntax|javascript|368236|entityMap^0|0|2|E|K|15|0|E|W|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Y|8|@$E|Z|F|10|G|H]|$E|11|F|12|G|H]]|9|@]|A|$]]|$1|I|3|J|5|D|7|13|8|@$E|14|F|15|G|H]]|9|@]|A|$]]|$1|K|3|L|5|6|7|16|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|19|8|@]|9|@]|A|$T|U]]|$1|V|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|W|$]]

I add here what worked for me, after a long time of searching:
<ol>
<li>Delete the <code>postmaster.pid</code> file:
<code>rm /usr/local/var/postgres/postmaster.pid</code>
</li>
<li>Restart your postgres:
<code>brew services restart postgresql</code>
</li>
</ol>
Hope this helps someone ...
Update 8/2022:
As Mike commented, for M1 Mac you would replace stage 1 with:
<pre><code>rm /opt/homebrew/var/postgresql/postmaster.pid
</code></pre>

blocks|key|1123699|text|这对我有用。首先定位postmaster.pid+(对我来说，它位于下面的var目录中，尽管它将根据操作系统的不同而有所不同)。然后摆脱postmaster.pid，然后终止postgres进程，然后启动/重新启动postgres服务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1123700|cd+/var/lib/pgsql/data/|offset|length|style|CODE|1123701|rm+postmaster.pid|1123702|sudo+pkill+-u+postgres|1123703|sudo+systemctl+start+postgresql.service|1123704|entityMap^0|0|0|N|0|0|H|0|0|M|0|0|13|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@$D|X|E|Y|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|Z|8|@$D|10|E|11|F|G]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|O|$]]

This worked for me. First locate postmaster.pid (for me it was in the var directory as seen below, although it will be different on depending on your operating system). Then get rid of postmaster.pid, then kill the postgres process, then start/restart postgres service.
<code>cd /var/lib/pgsql/data/</code>
<code>rm postmaster.pid</code>
<code>sudo pkill -u postgres</code>
<code>sudo systemctl start postgresql.service</code>

blocks|key|368302|text|在运行以下命令之后|type|unstyled|depth|inlineStyleRanges|entityRanges|data|368303|rm+/usr/local/var/postgres/postmaster.pid

brew+services+restart+postgresql|code-block|syntax|javascript|368304|错误lock+file+"postmaster.pid"+already+exists再次出现。|offset|length|style|CODE|368305|当我们运行launchctl+list+%7C+grep+postgres时|368306|28618+++0+++homebrew.mxcl.postgresql|368307|现有文件"postmaster.pid“是由launchctl托管的守护进程创建的。|368308|我们试图阻止homebrew.mxcl.postgresql通过|368309|sudo+launchctl+stop+homebrew.mxcl.postgresql
launchctl+disable+homebrew.mxcl.postgresql|368310|不幸的是，他们都无法阻止homebrew.mxcl.postgresql。|368311|原因是Disable+and+enable+an+agent+using+(persists+between+boots)|368312|https://apple.stackexchange.com/questions/105892/disable-services-in-osx-services-msc|368313|launchctl+enable+<name>+or+launchctl+disable+<name>|368314|当错误lock+file+"postmaster.pid"+already+exists再次出现时，有两种解决方法|368315|为了使立即停止代理，通过|unordered-list-item|BOLD|368316|launchctl+kill+homebrew.mxcl.postgresql|368317|重新启动桌面并运行brew+services+start+postgresql@14。现在，PostgreSQL可以成功启动了。|368318|希望这能对再次遇到同样问题的人有所帮助。|368319|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2|15|0|5|U|0|0|M|9|0|6|O|0|0|C|O|0|3|1M|0|0|2D|0|0|0|1F|0|3|15|0|3|7|0|0|0|6|9|X|0|0^^$0|@$1|2|3|4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1O|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1P|8|@$I|1Q|J|1R|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1S|8|@$I|1T|J|1U|K|L]]|9|@]|A|$]]|$1|O|3|P|5|D|7|1V|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|1W|8|@$I|1X|J|1Y|K|L]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1Z|8|@$I|20|J|21|K|L]]|9|@]|A|$]]|$1|U|3|V|5|D|7|22|8|@]|9|@]|A|$E|F]]|$1|W|3|X|5|6|7|23|8|@$I|24|J|25|K|L]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|26|8|@$I|27|J|28|K|L]]|9|@]|A|$]]|$1|10|3|11|5|6|7|29|8|@]|9|@$I|2A|J|2B|1|2C]]|A|$]]|$1|12|3|13|5|6|7|2D|8|@$I|2E|J|2F|K|L]]|9|@]|A|$]]|$1|14|3|15|5|6|7|2G|8|@$I|2H|J|2I|K|L]]|9|@]|A|$]]|$1|16|3|17|5|18|7|2J|8|@$I|2K|J|2L|K|19]]|9|@]|A|$]]|$1|1A|3|1B|5|D|7|2M|8|@]|9|@]|A|$E|F]]|$1|1C|3|1D|5|18|7|2N|8|@$I|2O|J|2P|K|19]|$I|2Q|J|2R|K|L]]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|2S|8|@]|9|@]|A|$]]|$1|1G|3|-4|5|6|7|2T|8|@]|9|@]|A|$]]]|1H|$1I|$5|1J|1K|1L|A|$1M|11]]]]

After running the following commands
<pre><code>rm /usr/local/var/postgres/postmaster.pid

brew services restart postgresql
</code></pre>
The error <code>lock file &quot;postmaster.pid&quot; already exists</code> comes up again.
<hr />
When we run <code>launchctl list | grep postgres</code>
<pre><code>28618 0 homebrew.mxcl.postgresql
</code></pre>
The existing file &quot;postmaster.pid&quot; was created by this daemon process hosted by <code>launchctl</code>.
We try to stop the <code>homebrew.mxcl.postgresql</code> through
<pre><code>sudo launchctl stop homebrew.mxcl.postgresql
launchctl disable homebrew.mxcl.postgresql
</code></pre>
Unfortunately, none of them could stop the <code>homebrew.mxcl.postgresql</code>.
The reason is <code>Disable and enable an agent using (persists between boots)</code>
<a href="https://apple.stackexchange.com/questions/105892/disable-services-in-osx-services-msc">https://apple.stackexchange.com/questions/105892/disable-services-in-osx-services-msc</a>
<code>launchctl enable &lt;name&gt; or launchctl disable &lt;name&gt;</code>
<hr />
Two ways to solve it when the error <code>lock file &quot;postmaster.pid&quot; already exists</code> comes up again
<ul>
<li>In order to stop an agent immediately through</li>
</ul>
<pre><code>launchctl kill homebrew.mxcl.postgresql
</code></pre>
<ul>
<li>Restart your desktop and run <code>brew services start postgresql@14</code>. Now, PostgreSQL could start successfully.</li>
</ul>
<hr />
Hope it could help someone who met the same issue again.

I have recently installed PostGIS on my Mac (El Capitan 10.11.4, Postgres is version 9.5.1) using Homebrew, and I am following these instructions - <a href="http://morphocode.com/how-to-install-postgis-on-mac-os-x/" rel="noreferrer">http://morphocode.com/how-to-install-postgis-on-mac-os-x/</a>

When I try to start Postgres using

<pre><code>pg_ctl -D /usr/local/var/postgres start 
</code></pre>

I get the following error:

<pre><code>$ FATAL: lock file "postmaster.pid" already exists
HINT: Is another postmaster (PID 280) running in data directory "/usr/local/var/postgres"?
</code></pre>

So I spent a few hours researching how to address this, but to no avail.

Notably, I tried to kill the PID as recommended in an answer on Superuser - <a href="https://superuser.com/questions/553045/fatal-lock-file-postmaster-pid-already-exists-">https://superuser.com/questions/553045/fatal-lock-file-postmaster-pid-already-exists-</a> (in the case above, I ran <code>kill 208</code>), but as soon as I tried to start Postgres again, I got the same error, albeit with a different PID number. I saw a few people recommended deleting the postmaster.pid file, but I feel like maybe I should save that as a last resort...

Admittedly part of the reason I'm not sure how to fix this is that I'm not really clear on what the postmaster even is - I'm just starting to learn about all of this.

Hopping into a Postgres database via the <code>psql db_name</code> command works just fine, for what it's worth.

FATAL ERROR lock file "postmaster.pid" already exists

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我最近在我的Mac上安装了PostGIS (El Capitan 10.11.4，Postgres是9.5.1版)，我使用了Homebrew，我按照下面的说明- 当我试图启动Postgres时pg_ctl -D /usr/local/var/postgres start 我得到以下错误：$ FATAL:  lock f...

问致命错误锁定文件"postmaster.pid“已经存在
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问致命错误锁定文件"postmaster.pid“已经存在EN