Re: The case when AsyncAppend exists also in the qual of Async ForeignScan - Mailing list pgsql-bugs

From Andrey Lepikhov
Subject Re: The case when AsyncAppend exists also in the qual of Async ForeignScan
Date
Msg-id 138b2b22-1f3e-5222-4eb6-86c562eeea8d@postgrespro.ru
Whole thread Raw
In response to Re: The case when AsyncAppend exists also in the qual of Async ForeignScan  (Etsuro Fujita <etsuro.fujita@gmail.com>)
Responses Re: The case when AsyncAppend exists also in the qual of Async ForeignScan  (Etsuro Fujita <etsuro.fujita@gmail.com>)
List pgsql-bugs
On 8/7/21 10:49, Etsuro Fujita wrote:
> I tried to reproduce this in my environment using HEAD and PG14, but I
> couldn't.  Could you elaborate a bit more on how to reproduce this?
Interesting...
I use the only script (see t.sql) right after the instance has started. 
Output see in t.out

All my specific preferences:
autovacuum = 'off'
max_worker_processes = 64
max_parallel_workers_per_gather = 16
max_parallel_workers = 32
parallel_setup_cost = 100
parallel_tuple_cost = 0.05
min_parallel_table_scan_size = 0

-- 
regards,
Andrey Lepikhov
Postgres Professional

Attachment

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #17094: FailedAssertion at planner.c
Next
From: Andrey Lepikhov
Date:
Subject: Re: The case when AsyncAppend exists also in the qual of Async ForeignScan