Postgres Quitting on my Server

Max Hattenback maxh at
Tue Jan 10 20:13:41 UTC 2023

Hey Das,

Can you check the logs in your postgres directory to see if anything is recorded around the time the database quits? You can change the configuration file to log more verbosely if there is nothing helpful there. I run postgres on windows so I'm not sure exactly where to look for the log file on a Mac install, but you should be able to figure it out fairly easily. The postgres config file will set a path for your logging directory.
From: omnisdev-en <omnisdev-en-bounces at> on behalf of Das Goravani <goravanis at>
Sent: Tuesday, January 10, 2023 3:08 PM
To: OmnisDev List - English <omnisdev-en at>
Subject: Postgres Quitting on my Server

I have a Mac server, Catalina, Postgres 13x

This installation of Postgres is somehow quitting after a couple hours of running fine.

It is half-launched after it quits, it is disabled.

When it is in this quit state, I have a few times issued the command to Run again. But it says it IS running. Yet it is non responsive to connections.  It is as if it quit.  I then issue the command to quit postgres, and it quits fully. Then I can relaunch it successfully.

So it gets disabled after a couple of hours. Exactly equal to as if it quit.

This has been sitting on my server this way for months. I posted about this before but didn’t make progress.

I feel now that I should perhaps install the latest upgrade, mainly to reinstall in hopes it then doesn’t "quit".

Do you have any input on the problem?

If not, do you have any advice about how to upgrade Postgres?

I saw before on here that Doug talked about how to upgrade Postgres so I thought it may have some quirks. In fact I don’t know how to make it "go" to the right version after installation of update.  I think that is the issue.

I plan on using the EDB installers I think they’re called.

Can you tell me how to look at tasks that are planned on the Mac Server?  Where are regular tasks located?  I mean by this where it might be recorded that Postgres should quit after a certain amount of time. I figure there might be such a thing, accessible through Terminal.. like "Cron Jobs" similar.  Any ideas on places that might have something recorded there that is affecting Postgres?

Perhaps a hacker or virus put in a command that disables Postgres after some time.

I know that normally Postgres stays running just fine, very reliable. This is true on my other Linux server. In fact I can’t find any support for this on the web, which is a testament to how well Postgres continues to run on a normal basis.

Manage your list subscriptions at
Start a new message -> mailto:omnisdev-en at


More information about the omnisdev-en mailing list