From: Andrei Lepikhov <lepihov@gmail.com>
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
Date: Thu, 22 Aug 2024 19:00:37 +0200
Message-ID: <59962b3b-4288-4759-a480-b60bcce3b388@gmail.com> (raw)
In-Reply-To: <18588-204730f9394441a8@postgresql.org>
References: <18588-204730f9394441a8@postgresql.org>
On 22/8/2024 14:58, PG Bug reporting form wrote:
> Index Scan using negotiation_topic_archive_p005_employer_id_resume_id_idx
> on negotiation_topic_archive_p005 this_ (cost=0.11..2501972.13 rows=505757
> width=8) (actual time=0.020..699.322 rows=510040 loops=1)
> Index Cond: (employer_id = 816144)
> Planning Time: 0.132 ms
> Execution Time: 717.005 ms
Can you disable IndexScan and Bitmapscan step-by-step and show explain
analyze verbose with costs?
--
regards, Andrei Lepikhov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: lepihov@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18588: Cannot force/let database use parallel execution in simple case.
In-Reply-To: <59962b3b-4288-4759-a480-b60bcce3b388@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox