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

From Peter Geoghegan
Subject Re: PostgreSQL crashes with SIGSEGV
Date
Msg-id CAH2-Wzk4MTSPWnCv3ENz9HZrtiJGut8TOtLTaf56AxmJ9VbcEA@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL crashes with SIGSEGV  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses Re: PostgreSQL crashes with SIGSEGV  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Re: PostgreSQL crashes with SIGSEGV  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Mar 26, 2018 at 5:14 AM, Kyotaro HORIGUCHI
<horiguchi.kyotaro@lab.ntt.co.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.

-- 
Peter Geoghegan


pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: PQHost() undefined behavior if connecting string contains bothhost and hostaddr types
Next
From: Thomas Munro
Date:
Subject: Re: [HACKERS] pg_serial early wraparound