Re: server crash in nodeAppend.c - Mailing list pgsql-hackers

From Robert Haas
Subject Re: server crash in nodeAppend.c
Date
Msg-id CA+Tgmoa-TTWwnW4+V9KCEwvEucSY=ijDYtA2HpGH3MmnJtmmaw@mail.gmail.com
Whole thread Raw
In response to server crash in nodeAppend.c  (Rajkumar Raghuwanshi <rajkumar.raghuwanshi@enterprisedb.com>)
Responses Re: server crash in nodeAppend.c
List pgsql-hackers
On Tue, Feb 27, 2018 at 5:24 AM, Rajkumar Raghuwanshi
<rajkumar.raghuwanshi@enterprisedb.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


pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: PATCH: Exclude temp relations from base backup
Next
From: Antonin Houska
Date:
Subject: Re: [HACKERS] WIP: Aggregation push-down