pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Aleksandr Parfenov <a.parfenov@postgrespro.ru>
To: pgsql-hackers@lists.postgresql.org
Cc: Peter Geoghegan <pg@bowt.ie>
Subject: Re: PostgreSQL crashes with SIGSEGV
Date: Tue, 16 Jan 2018 07:52:26 +0000
Message-ID: <151608914608.25640.2144132915573008595.pgcf@coridan.postgresql.org> (raw)
In-Reply-To: <CAH2-WzmxBVYUrqtmOyP9jB1j2ZO7xTpPx65ZKTO362Qg0MRgxA@mail.gmail.com>
References: <1512661638.9720.34.camel@oopsware.de>
	<CAH2-WzmxBVYUrqtmOyP9jB1j2ZO7xTpPx65ZKTO362Qg0MRgxA@mail.gmail.com>

The following review has been posted through the commitfest application:
make installcheck-world:  tested, passed
Implements feature:       tested, passed
Spec compliant:           tested, passed
Documentation:            tested, passed

Hi,

All information is related to WIP-tuplesort-memcontext-fix.patch.
The patch applies and fixes the bug on REL9_6_STABLE and LGTM.

However, REL9_5_STABLE affected as well and the patch doesn't applicable to it.
But it may be another entry because the difference in tuplesort may cause some changes in the fix too.

The new status of this patch is: Ready for Committer


view thread (33+ messages)  latest in thread

Message-ID: <151608914608.25640.2144132915573008595.pgcf@coridan.postgresql.org>
Permalink:  ../151608914608.25640.2144132915573008595.pgcf@coridan.postgresql.org/
Also on:    postgresql.org/message-id/151608914608.25640.2144132915573008595.pgcf@coridan.postgresql.org

 · 

reply

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: a.parfenov@postgrespro.ru, pgsql-hackers@lists.postgresql.org, pg@bowt.ie
  Subject: Re: PostgreSQL crashes with SIGSEGV
  In-Reply-To: <151608914608.25640.2144132915573008595.pgcf@coridan.postgresql.org>

* 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