Re: why not parallel seq scan for slow functions

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: why not parallel seq scan for slow functions
Date: 2017-09-19 20:17:50
Message-ID: CAEepm=1KhZg17t6tNpFZ6pr=ucxa-kF24m9cEASU3cj3g_2zgg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 14, 2017 at 3:19 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> The attached patch fixes both the review comments as discussed above.

This cost stuff looks unstable:

test select_parallel ... FAILED

! Gather (cost=0.00..623882.94 rows=9976 width=8)
Workers Planned: 4
! -> Parallel Seq Scan on tenk1 (cost=0.00..623882.94 rows=2494 width=8)
(3 rows)

drop function costly_func(var1 integer);
--- 112,120 ----
explain select ten, costly_func(ten) from tenk1;
QUERY PLAN
----------------------------------------------------------------------------
! Gather (cost=0.00..625383.00 rows=10000 width=8)
Workers Planned: 4
! -> Parallel Seq Scan on tenk1 (cost=0.00..625383.00 rows=2500 width=8)
(3 rows)

drop function costly_func(var1 integer);

From https://travis-ci.org/postgresql-cfbot/postgresql/builds/277376953 .

--
Thomas Munro
http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashwin Agrawal 2017-09-19 20:23:58 "inconsistent page found" with checksum and wal_consistency_checking enabled
Previous Message Tom Lane 2017-09-19 20:16:33 Re: Show backtrace when tap tests fail