Re: Server process exited with exit code 4

From: yangsr3411 <yangsr3411(at)163(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Server process exited with exit code 4
Date: 2023-11-09 01:41:28
Message-ID: 299d62b1.3e25a.18bb1bdcd62.Coremail.yangsr3411@163.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Finally, we used the Windows tool Gflags.exe and found that other software terminated the postgres process.

---- Replied Message ----
| From | yangsr3411<yangsr3411(at)163(dot)com> |
| Date | 10/30/2023 19:07 |
| To | pgsql-general<pgsql-general(at)postgresql(dot)org> |
| Cc | |
| Subject | Fw: Server process exited with exit code 4 |
it doesn't seem like a hardware issue because we have over 20 machines running and 5 of them have been experiencing this issue recently.

we have encountered problems before with antivirus software causing the database to hang, so we are also considering if other software on the Windows operating system is interfering.

---- Forwarded Message ----
| From | Justin Clift<justin(at)postgresql(dot)org> |
| Date | 10/30/2023 14:29 |
| To | yangsr3411<yangsr3411(at)163(dot)com> |
| Cc | pgsql-general<pgsql-general(at)postgresql(dot)org> |
| Subject | Re: Server process exited with exit code 4 |
On 2023-10-30 14:02, yangsr3411 wrote:
<snip>
> Has anyone encountered similar problem or may know a solution?

Just to rule out hardware problems, does the server hardware have
some way of showing things like ECC memory errors and similar?

Most official server hardware (HPE, Dell, etc) have utilities
that can show a log of any recent weirdness that occurred at a
hardware level.

If yours can, take a look for things like ECC errors or any other
strange stuff. :)

Regards and best wishes,

Justin Clift

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Chris Travers 2023-11-09 05:08:09 NUMA, PostgreSQL and docker images
Previous Message Tom Lane 2023-11-08 21:36:31 Re: Weirdness (bug?) with aggregates and subqueries