The case when AsyncAppend exists also in the qual of Async ForeignScan

From: Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org, Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
Subject: The case when AsyncAppend exists also in the qual of Async ForeignScan
Date: 2021-07-02 13:24:53
Message-ID: fe5eaa19-1704-e4a4-76ee-3b9d37ade399@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

I found one bug. Look at the case:

CREATE TABLE test (x int) PARTITION BY HASH (x);
CREATE TABLE test_1 (x int);
CREATE TABLE test_2 (x int);
CREATE FOREIGN TABLE ftest_1 PARTITION OF test
FOR VALUES WITH (modulus 2, remainder 0)
SERVER loopback OPTIONS (table_name 'test_1');
CREATE FOREIGN TABLE ftest_2 PARTITION OF test
FOR VALUES WITH (modulus 2, remainder 1)
SERVER loopback2 OPTIONS (table_name 'test_2');
INSERT INTO test (SELECT * FROM generate_series(1,10));
ANALYZE test,test_1,test_2,ftest_1,ftest_2;

EXPLAIN (ANALYZE)
SELECT * FROM test WHERE x NOT IN (
SELECT avg(x) FROM test WHERE x > 10
);
ERROR: InstrEndLoop called on running node

When I added ', COSTS OFF, SUMMARY OFF, TIMING OFF' this example fall
down into the SEGFAULT.

I prepared quick fix for this problem (see patch in attachment). Maybe
it is'nt a best solution but it can speedup search of it.

--
regards,
Andrey Lepikhov
Postgres Professional

Attachment Content-Type Size
0001-Do-not-take-a-tuple-immediately-after-finishing-of-a.patch text/plain 8.0 KB

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2021-07-02 13:50:17 Re: BUG #17081: Segmentation fault on _PG_init() in a session_preload_library
Previous Message Martin Butter 2021-07-02 07:15:02 Re: BUG #17081: Segmentation fault on _PG_init() in a session_preload_library