Re: server crash in nodeAppend.c

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: server crash in nodeAppend.c
Date: 2018-02-28 15:59:22
Message-ID: CA+Tgmoa-TTWwnW4+V9KCEwvEucSY=ijDYtA2HpGH3MmnJtmmaw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 27, 2018 at 5:24 AM, Rajkumar Raghuwanshi
<rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com> wrote:
> SET parallel_setup_cost=0;
> SET parallel_tuple_cost=0;
> create or replace function foobar() returns setof text as
> $$ select 'foo'::varchar union all select 'bar'::varchar ; $$
> language sql stable;
>
> postgres=# select foobar();
> server closed the connection unexpectedly
> This probably means the server terminated abnormally
> before or while processing the request.
> The connection to the server was lost. Attempting reset: Failed.
>
> --logfile
> 2018-02-26 22:15:52.908 IST [61738] LOG: database system is ready to accept
> connections
> TRAP: FailedAssertion("!(whichplan >= 0 && whichplan <= node->as_nplans)",
> File: "nodeAppend.c", Line: 365)
> 2018-02-26 22:17:50.441 IST [61738] LOG: server process (PID 61748) was
> terminated by signal 6: Aborted
> 2018-02-26 22:17:50.441 IST [61738] DETAIL: Failed process was running:
> select foobar();

Nice test case. I pushed commit
ce1663cdcdbd9bf15c81570277f70571b3727dd3, including your test case, to
fix this.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Antonin Houska 2018-02-28 16:02:43 Re: [HACKERS] WIP: Aggregation push-down
Previous Message David Steele 2018-02-28 15:55:10 PATCH: Exclude temp relations from base backup