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

From Peter Geoghegan
Subject Re: PostgreSQL crashes with SIGSEGV
Date
Msg-id CAH2-WzkYZy633TUDQ6Uc-vq9uUj-57vFFKmZ5jGCskw47mJfLA@mail.gmail.com
Whole thread Raw
In response to PostgreSQL crashes with SIGSEGV  (Bernd Helmle <mailings@oopsware.de>)
Responses Re: PostgreSQL crashes with SIGSEGV  (Bernd Helmle <mailings@oopsware.de>)
List pgsql-bugs
On Thu, Dec 7, 2017 at 7:47 AM, Bernd Helmle <mailings@oopsware.de> wrote:
> I've tested this so far against very current REL9_6_STABLE and
> REL9_5_STABLE and got them to crash with the same backtrace. The crash
> is dependent on the chosen plan, experiments with work_mem show that
> the crash seems to happen only if you get external sorts into the
> execution plan.
>
> REL10_STABLE seems not affected, as my extracted application query
> doesn't crash there.

Does "set replacement_sort_tuples = 0" change anything on
REL9_6_STABLE? If you only get a crash when there is very little
work_mem, then that might be a good avenue of investigation. Note that
my changes to external sorting started in REL9_6_STABLE, so they can't
be involved here.

Are you aware of commit 512f67c8d02cc558f9c269cc848b0f0f788c4fe1,
which fixed a bug affecting external sorts? Are you sure that you have
that fix on REL9_5_STABLE + REL9_6_STABLE?

-- 
Peter Geoghegan


pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: PostgreSQL crashes with SIGSEGV
Next
From: Peter Geoghegan
Date:
Subject: Re: PostgreSQL crashes with SIGSEGV