Re: PostgreSQL crashes with SIGSEGV

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Aleksandr Parfenov <a.parfenov@postgrespro.ru>

Cc: pgsql-hackers@lists.postgresql.org, Peter Geoghegan <pg@bowt.ie>

Date: 2018-01-17T19:23:18Z

Lists: pgsql-bugs, pgsql-hackers

Aleksandr Parfenov <a.parfenov@postgrespro.ru> writes:
> The new status of this patch is: Ready for Committer

I don't feel particularly comfortable committing a patch that
was clearly labeled as a rushed draft by its author.
Peter, where do you stand on this work?

In a quick look at the patches, WIP-kludge-fix.patch seems clearly
unacceptable for back-patching because it changes the signature and
behavior of ExecResetTupleTable, which external code might well be using.

			regards, tom lane

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