Re: PostgreSQL crashes with SIGSEGV

Peter Geoghegan <pg@bowt.ie>

From: Peter Geoghegan <pg@bowt.ie>

To: Michael Paquier <michael.paquier@gmail.com>

Cc: Andreas Seltenreich <andreas.seltenreich@credativ.de>, Bernd Helmle <mailings@oopsware.de>, PostgreSQL mailing lists <pgsql-bugs@postgresql.org>

Date: 2017-12-17T15:46:56Z

Lists: pgsql-bugs, pgsql-hackers

On Sun, Dec 17, 2017 at 2:46 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> Could you add that to the next commit fest registered as a bug fix? We
> don't want to lose track of that and this should be reviewed.

Done.

-- 
Peter Geoghegan

Commits

Fix actual and potential double-frees around tuplesort usage.
- c2d4eb1b1fa2 11.0 landed
- e4ff711582b1 9.5.13 landed
- c98f218fbf5a 10.4 landed
- 90decdba3786 9.6.9 landed
Allow the built-in ordered-set aggregates to share transition state.
- be0ebb65f512 11.0 cited
Avoid integer overflow while sifting-up a heap in tuplesort.c.
- 512f67c8d02c 10.0 cited
Allow avoiding tuple copy within tuplesort_gettupleslot().
- fa117ee40330 10.0 cited
Remove should_free arguments to tuplesort routines.
- 3856cf9607f4 10.0 cited
Fix use-after-free around DISTINCT transition function calls.
- a5f0bd77a2fa 9.6.1 cited
- d8589946ddd5 10.0 cited
Reuse abbreviated keys in ordered [set] aggregates.
- f1f5ec1efafe 9.6.0 cited