Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1shEnZ-00F3z4-OJ for pgsql-bugs@arkaria.postgresql.org; Thu, 22 Aug 2024 20:52:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1shEnX-005TTV-7P for pgsql-bugs@arkaria.postgresql.org; Thu, 22 Aug 2024 20:52:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1shEnW-005TTN-V2 for pgsql-bugs@lists.postgresql.org; Thu, 22 Aug 2024 20:52:47 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1shEnT-0010VM-OS for pgsql-bugs@lists.postgresql.org; Thu, 22 Aug 2024 20:52:46 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 47MKqh6t2074137; Thu, 22 Aug 2024 16:52:43 -0400 From: Tom Lane To: Maxim Boguk cc: David Rowley , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18588: Cannot force/let database use parallel execution in simple case. In-reply-to: References: <18588-204730f9394441a8@postgresql.org> <2059550.1724353316@sss.pgh.pa.us> Comments: In-reply-to Maxim Boguk message dated "Thu, 22 Aug 2024 23:27:24 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2074135.1724359963.1@sss.pgh.pa.us> Date: Thu, 22 Aug 2024 16:52:43 -0400 Message-ID: <2074136.1724359963@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Maxim Boguk writes: > With sufficiently large table - I didn't manage find a combinations of > settings to force parallel execution (im my real case - the database huge > and mostly cold on ssd raid - so parallel execution provides almost linear > speedup with amount of parallel workers even on 1000 rows... not talking > about 10k-10m rows, but I cannot convince the PostgreSQL use parallel index > scan for 2m returned rows case). Well, there may be something going on in your real case that isn't apparent from this toy example. Perhaps look for a better example? regards, tom lane