From: Bernd Helmle <mailings@oopsware.de>
To: Peter Geoghegan <pg@bowt.ie>
Cc: pgsql-bugs@postgresql.org
Subject: Re: PostgreSQL crashes with SIGSEGV
Date: Fri, 08 Dec 2017 10:13:00 +0100
Message-ID: <1512724380.9720.37.camel@oopsware.de> (raw)
In-Reply-To: <CAH2-WzkYZy633TUDQ6Uc-vq9uUj-57vFFKmZ5jGCskw47mJfLA@mail.gmail.com>
References: <1512661638.9720.34.camel@oopsware.de>
<CAH2-WzkYZy633TUDQ6Uc-vq9uUj-57vFFKmZ5jGCskw47mJfLA@mail.gmail.com>
Am Donnerstag, den 07.12.2017, 18:23 -0800 schrieb Peter Geoghegan:
> 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.
>
replacement_sort_tuples = 0 changes the picture, indeed. With that
setting, the query runs without problems in REL9_6_STABLE.
> 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?
My test instances are build against a fresh pull from yesterday.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: mailings@oopsware.de, pg@bowt.ie
Subject: Re: PostgreSQL crashes with SIGSEGV
In-Reply-To: <1512724380.9720.37.camel@oopsware.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox