Re: PostgreSQL crashes with SIGSEGV

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, Aleksandr Parfenov <a(dot)parfenov(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: PostgreSQL crashes with SIGSEGV
Date: 2018-03-28 17:33:54
Message-ID: CAH2-WzmbQVRTYYk=fO=_O+8EBnrwr7xQQ+rH+O8J3W7o=gxn_g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Wed, Mar 28, 2018 at 10:30 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> It looks good to me. The only real objection would be if someone came
> up with a test case proving that there's a significant performance
> degradation from the extra copies. But given that these are back
> branches, it would take a pretty steep penalty for me to want to take
> the risk of refactoring to avoid that.
>
> I've pushed it with some cosmetic adjustments.

Thank you, Tom.

--
Peter Geoghegan

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Angga Wirapraditya 2018-03-28 17:47:51 Code Igniter 3.16 Error Get Last Insert Id
Previous Message Tom Lane 2018-03-28 17:30:49 Re: PostgreSQL crashes with SIGSEGV

Browse pgsql-hackers by date

  From Date Subject
Next Message Konstantin Knizhnik 2018-03-28 17:36:32 Re: disable SSL compression?
Previous Message Tom Lane 2018-03-28 17:30:49 Re: PostgreSQL crashes with SIGSEGV