From: Tom Lane <tgl@sss.pgh.pa.us>
To: ChiJin Zhou <tlock.chijin@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Buffer overflow when continuously send SIGHUP to postgres
Date: Tue, 14 Apr 2020 11:48:52 -0400
Message-ID: <21998.1586879332@sss.pgh.pa.us> (raw)
In-Reply-To: <CAA8ZSMqAHDCgo07hqKoM5XJaoQy6Vv76O7966agez4ffyQktkA@mail.gmail.com>
References: <CAA8ZSMqAHDCgo07hqKoM5XJaoQy6Vv76O7966agez4ffyQktkA@mail.gmail.com>
ChiJin Zhou <tlock.chijin@gmail.com> 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=postgresql.git&a=commitdiff&h=9abb2bfc0
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, tlock.chijin@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Buffer overflow when continuously send SIGHUP to postgres
In-Reply-To: <21998.1586879332@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox