Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jONo1-00064j-F9 for pgsql-bugs@arkaria.postgresql.org; Tue, 14 Apr 2020 15:48:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jONo0-000329-AY for pgsql-bugs@arkaria.postgresql.org; Tue, 14 Apr 2020 15:48:56 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jONo0-00030T-4U for pgsql-bugs@lists.postgresql.org; Tue, 14 Apr 2020 15:48:56 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jONnx-0000gy-VA for pgsql-bugs@lists.postgresql.org; Tue, 14 Apr 2020 15:48:55 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 03EFmqiE021999; Tue, 14 Apr 2020 11:48:52 -0400 From: Tom Lane To: ChiJin Zhou cc: pgsql-bugs@lists.postgresql.org Subject: Re: Buffer overflow when continuously send SIGHUP to postgres In-reply-to: References: Comments: In-reply-to ChiJin Zhou message dated "Tue, 14 Apr 2020 11:42:49 +0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <21997.1586879332.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 14 Apr 2020 11:48:52 -0400 Message-ID: <21998.1586879332@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk ChiJin Zhou writes: > 3. continuously send SIGHUP to the server process like: > 4. and the server process exit with address boundary error. This was fixed in HEAD at [1]. Our current thought is not to back-patch that, though, as it doesn't seem like a case likely to be much of a problem in practice, and the patch has not yet survived a beta test cycle so it's not risk-free. regards, tom lane [1] https://git.postgresql.org/gitweb/?p=3Dpostgresql.git&a=3Dcommitdiff&h= =3D9abb2bfc0