| From: | Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru> |
|---|---|
| To: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: The case when AsyncAppend exists also in the qual of Async ForeignScan |
| Date: | 2021-07-08 10:18:49 |
| Message-ID: | 138b2b22-1f3e-5222-4eb6-86c562eeea8d@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 | Content-Type | Size |
|---|---|---|
| t.sql | application/sql | 954 bytes |
| t.out | text/plain | 517 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Lepikhov | 2021-07-08 10:32:38 | Re: The case when AsyncAppend exists also in the qual of Async ForeignScan |
| Previous Message | PG Bug reporting form | 2021-07-08 08:33:07 | BUG #17094: FailedAssertion at planner.c |