Yes making the file is the problem. If you read my topic again, then you may
know about what is the exact question
--
View this message in context:
http://postgresql.nabble.com/How-to-open-PGStrom-an-extension-of-PostgreSQL-in-Netbeans-tp5931425p5931594.html
Sent from the PostgreSQL - general m
Nope. I am not asking about installation instructions. I have installed it.
And I know how to run it from command line.
I just wanted to compile it in netbeans.
--
View this message in context:
http://postgresql.nabble.com/How-to-open-PGStrom-an-extension-of-PostgreSQL-in-Netbeans-tp5931425p59
PostgreSQL has been successfully compiled in netbeans 8.1. But how to add its
extension PG_Strom into it?
--
View this message in context:
http://postgresql.nabble.com/How-to-open-PGStrom-an-extension-of-PostgreSQL-in-Netbeans-tp5931425p5931427.html
Sent from the PostgreSQL - general mailing li
Considering PGStrom, an extension of PostgreSQL-9.5.4, I tried opening that
file in netbeans 8.1
I opened PGStrom in netbeans as File -> New Project -> C/C++ -> C/C++
Project with Existing Sources. And then selected the Folder that contains
existing sources (PG_Strom). And then Finish
It is showi
What are the functions (for example) are available/not available to get
transformed to GPU source code?
What is the factor value u consider to get multiplied with actual cost for
CPU? For example, default cpu_tuple_cost is 0.01.
Consider, for example, if the cost=0.00..458.00 for seq scan, how c
"fraction of the cost of executing the same portion of the plan using
the traditional CPU processing"
Can u explain about this fraction in detail?
I need the clarifications for query plan tree also.
Executing a query in CPU is different from executing the same in GPU. So the
plan also differs.
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 a
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?
--
View this message in context:
http://postgresql.nabble.com/How-the-Planner-in-PGStrom-differs-from-Postg
Thanks for your response.
But that planning for a query execution in GPU is different from planning a
query execution in CPU right?
Even considering cost calculation, cost for executing a query in GPU is
different from cost for executing a query in CPU. How this cost calculation
for GPU occurs?
Yeah I think Kouhei Kaigai is one of the Contributors. So expecting his
reply.
And thanks for your kind responses
--
View this message in context:
http://postgresql.nabble.com/How-the-Planner-in-PGStrom-differs-from-PostgreSQL-tp5929724p5930373.html
Sent from the PostgreSQL - general mailing l
Thank you so much for your references.
How the planning factors of PGStrom differs from planning factos of
PostgreSQL?
--
View this message in context:
http://postgresql.nabble.com/How-the-Planner-in-PGStrom-differs-from-PostgreSQL-tp5929724p5930356.html
Sent from the PostgreSQL - general mail
Thank you so much for your kind reply.
I am just curious about this planning factors in GPU.
There can be more than one appropriate paths in query plan tree. How the
decision for particular path has been made considering those planning
factors?
--
View this message in context:
http://p
I am reading through Postgres and PGStrom. Regarding the planning factors, I
need some clarifications. Can u help me with that?
Planner in Postgres checks for different scan and join methods, and then
find the cheapest one and creates a query plan tree. While going for same
thing in GPU, the check
13 matches
Mail list logo