Re: PostgreSQL crashes with SIGSEGV

From: Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
To: pg(at)bowt(dot)ie
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, a(dot)parfenov(at)postgrespro(dot)ru, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: PostgreSQL crashes with SIGSEGV
Date: 2018-03-27 09:23:59
Message-ID: 20180327.182359.209998262.horiguchi.kyotaro@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

At Mon, 26 Mar 2018 20:40:51 -0700, Peter Geoghegan <pg(at)bowt(dot)ie> wrote in <CAH2-Wzk4MTSPWnCv3ENz9HZrtiJGut8TOtLTaf56AxmJ9VbcEA(at)mail(dot)gmail(dot)com>
> On Mon, Mar 26, 2018 at 5:14 AM, Kyotaro HORIGUCHI
> <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> >> Attached patches do it that way. I'm happy with what I came up with,
> >> which is a lot simpler than my first approach. The extra copying seems
> >> likely to be well worth it, since it is fairly isolated in practice,
> >> especially on 9.6. There is no extra copying from v10+, since they
> >> don't need the first fix at all.
>
> > If no one objects, I'll mark this as Ready for Commit in a couple
> > of days.
>
> Thank you for the review, Horiguchi-san. It's hard to decide how
> important each goal is when coming up with a back-patchable fix like
> this. When the goals are somewhat in competition with each other, a
> second or a third opinion is particularly appreciated.

Understood. I'll wait for the other opinions.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-03-27 23:42:59 BUG #15131: "ERROR: function pg_current_xlog_location() does not exist" in PGAdmin III
Previous Message Peter Geoghegan 2018-03-27 03:40:51 Re: PostgreSQL crashes with SIGSEGV

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavan Deolasee 2018-03-27 09:28:36 Re: [HACKERS] MERGE SQL Statement for PG11
Previous Message Kyotaro HORIGUCHI 2018-03-27 09:21:44 Re: PQHost() undefined behavior if connecting string contains both host and hostaddr types