Re: PostgreSQL crashes with SIGSEGV - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PostgreSQL crashes with SIGSEGV
Date
Msg-id 6358.1516222816@sss.pgh.pa.us
Whole thread Raw
In response to Re: PostgreSQL crashes with SIGSEGV  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: PostgreSQL crashes with SIGSEGV
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Nikolay Shaplov
Date:
Subject: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOAST table does not exist
Next
From: Andrew Dunstan
Date:
Subject: Re: jsonpath