Eric Hill <Eric.Hill@xxxxxxx> writes: > 2021-04-23 03:20:57 EDT [5324]: LOG: connection received: host=10.120.80.162 port=54017 > 2021-04-23 03:20:57 EDT [5324]: LOG: connection authorized: user=dba_webjmp database=webjmp > 2021-04-23 03:21:00 EDT [15776]: LOG: server process (PID 14820) exited with exit code 1 > 2021-04-23 03:21:00 EDT [15776]: DETAIL: Failed process was running: SET client_min_messages TO warning;SET TIME ZONE INTERVAL '+00:00' HOUR TO MINUTE; > 2021-04-23 03:21:00 EDT [15776]: LOG: terminating any other active server processes Hm. That's fairly odd. Exit code 1 ordinarily means that the backend hit a "FATAL" error, which is one that causes process termination but *not* a database-wide restart. The fact that the postmaster is treating it that way anyway implies that the backend failed to disarm the "dead man switch" mechanism that exists to check that backends cleaned up their shared-memory state before exiting. Another thing that doesn't square with this being an ordinary FATAL exit is that there's no message visible in the log. (I wonder what this looks like from the client's end --- is it getting any sort of termination message, or just a lost network connection?) The implication is that something in the backend did _exit(1) to force process termination without any of the normal atexit cleanup. There is not, or at least isn't supposed to be, anything in Postgres proper that does that. So I'm wondering if you have any nonstandard code in there, such as unusual extensions. A badly-written event trigger could perhaps do it too. This being Windows, a certain amount of suspicion has to be directed towards bogus antivirus code, too. regards, tom lane
