From: Andrew Gierth <andrew@tao11.riddles.org.uk>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Andreas Seltenreich <andreas.seltenreich@credativ.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: obeltrame@callixbrasil.com, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #15053: SIGSEGV - While executing query with cube agregator
Date: Wed, 07 Feb 2018 11:24:54 +0000
Message-ID: <878tc5t5h1.fsf@news-spur.riddles.org.uk> (raw)
In-Reply-To: <CAH2-WzmzAXFBa=RvCm5_DKb=en8cUg5Hag2FwWTcoguKDuv__w@mail.gmail.com>
References: <151793838713.1243.5246278119990227987@wrigleys.postgresql.org>
<23669.1517944780@sss.pgh.pa.us>
<87wozpye0g.fsf@credativ.de>
<CAH2-WzmzAXFBa=RvCm5_DKb=en8cUg5Hag2FwWTcoguKDuv__w@mail.gmail.com>
>>>>> "Peter" == Peter Geoghegan <pg@bowt.ie> writes:
> On Tue, Feb 6, 2018 at 2:00 PM, Andreas Seltenreich
> <andreas.seltenreich@credativ.de> wrote:
>> backtrace and query look similar to the issue we reported leading to the
>> following commitfest entry:
>>
>> https://commitfest.postgresql.org/16/1413/
Peter> I suspect the same.
I just eyeballed that. The obvious question that comes to mind is, can't
this issue be fixed in nodeAgg rather than monkeying with the slot code?
--
Andrew (irc:RhodiumToad)
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: andrew@tao11.riddles.org.uk, pg@bowt.ie, andreas.seltenreich@credativ.de, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15053: SIGSEGV - While executing query with cube agregator
In-Reply-To: <878tc5t5h1.fsf@news-spur.riddles.org.uk>
* 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