Re: How the Planner in PGStrom differs from PostgreSQL? - Mailing list pgsql-general

From Mark Anns
Subject Re: How the Planner in PGStrom differs from PostgreSQL?
Date
Msg-id 1479377371828-5930783.post@n3.nabble.com
Whole thread Raw
In response to Re: How the Planner in PGStrom differs from PostgreSQL?  (Kouhei Kaigai <kaigai@ak.jp.nec.com>)
Responses Re: How the Planner in PGStrom differs from PostgreSQL?  (Amit Langote <amitlangote09@gmail.com>)
Re: How the Planner in PGStrom differs from PostgreSQL?  (Kouhei Kaigai <kaigai@ak.jp.nec.com>)
List pgsql-general
Can u explain this statement "check whether the scan qualifier can
be executable on GPU device"

What are the scan qualifiers?

How to determine whether they are device executable or not?

The cost estimates are entirely based on number of rows and type of scan.
Then it will be same for both CPU and GPU. How the decision can be made for
cheaper one comparing CPU and GPU estimates?




--
View this message in context:
http://postgresql.nabble.com/How-the-Planner-in-PGStrom-differs-from-PostgreSQL-tp5929724p5930783.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.


pgsql-general by date:

Previous
From: Mark Anns
Date:
Subject: Re: How the Planner in PGStrom differs from PostgreSQL?
Next
From: Andy Halsall
Date:
Subject: Re: libpq backwards compatbility