From: Tom Lane <tgl@sss.pgh.pa.us>
To: Lynn Carol Johnson <lcj34@cornell.edu>
cc: "pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>
Subject: Re: Postgres dying after many failed logins
In-reply-to: <58143128-71A6-4C51-9BCD-35105A385FA8@cornell.edu>
References: <58143128-71A6-4C51-9BCD-35105A385FA8@cornell.edu>
Comments: In-reply-to Lynn Carol Johnson <lcj34@cornell.edu>
	message dated "Mon, 08 Nov 2021 12:45:07 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <890132.1636383644.1@sss.pgh.pa.us>
Date: Mon, 08 Nov 2021 10:00:44 -0500
Message-ID: <890133.1636383644@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/890133.1636383644%40sss.pgh.pa.us>
Precedence: bulk

Lynn Carol Johnson <lcj34@cornell.edu> writes:
> My question:  Is this expected behavior, ie that the server will
> shutdown after hours of failed attempts?

There is nothing built-in that would cause that, and frankly I doubt
that there is any direct connection.  It could be that the AWS environment
imposes some resource limit (i.e., total number of child processes
spawned) that the postmaster is eventually hitting because of the
hack attempts.  However, if that's true, I wouldn't really expect it to
manifest as anything as polite as a SIGTERM signal.  So I think there
is something else going on.  You need to look for what in your environment
could send the postmaster a SIGTERM.  Can you correlate the shutdown with
anything?  One thing I'm wondering is if it matches the time of shutdown
of whatever you're launching the postmaster with.

			regards, tom lane