From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@bowt.ie>
cc: Aleksandr Parfenov <a.parfenov@postgrespro.ru>,
        PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: PostgreSQL crashes with SIGSEGV
In-reply-to: 
 <CAH2-WzkQzCaEkvdk2vyD1kNaKtTdYAM4r62krPFtytjxEu8A1A@mail.gmail.com>
References: <1512661638.9720.34.camel@oopsware.de>
 <CAH2-WzmxBVYUrqtmOyP9jB1j2ZO7xTpPx65ZKTO362Qg0MRgxA@mail.gmail.com>
 <151608914608.25640.2144132915573008595.pgcf@coridan.postgresql.org>
 <14267.1516216998@sss.pgh.pa.us>
 <CAH2-WzmAKo=KoBJrTB0M7UUnM-L=Gycs_=iT8+Z2YohmxEbFWg@mail.gmail.com>
 <4977.1516221082@sss.pgh.pa.us>
 <CAH2-WzkQzCaEkvdk2vyD1kNaKtTdYAM4r62krPFtytjxEu8A1A@mail.gmail.com>
Comments: In-reply-to Peter Geoghegan <pg@bowt.ie>
	message dated "Wed, 17 Jan 2018 12:41:13 -0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6357.1516222816.1@sss.pgh.pa.us>
Date: Wed, 17 Jan 2018 16:00:16 -0500
Message-ID: <6358.1516222816@sss.pgh.pa.us>
Precedence: bulk

Peter Geoghegan <pg@bowt.ie> writes:
> On Wed, Jan 17, 2018 at 12:31 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> +1.  If the problem isn't known to be reproducible in those branches,
>> the risk of adding new bugs seems to outweigh any benefit.

> You could make the same objection to changing tuplesort_getdatum()
> outside of the master branch, though. I think that going back further
> than that for the (arguably independent) tuplesort_getdatum() subset
> fix might still be a good idea. I wonder where you stand on this.

I haven't been following the thread very closely, so I don't have an
opinion on that.

			regards, tom lane