EXPLAIN VERBOSE "FDW Time" does not look right
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with the EXPLAIN (ANALYZE, VERBOSE) output and the reported FDW Time for the supplied COUNT query. Trace how pg_clickhouse records planning and execution timing, then compare it with PostgreSQL's Planning Time and Execution Time. Done means the FDW Time value accurately reflects the intended timing scope.
Written by the indexing model from the issue text.
Description
Example:
EXPLAIN (ANALYZE, VERBOSE) SELECT COUNT(*) FROM hits WHERE "URL" LIKE '%google%';
Foreign Scan (cost=1.00..0.20 rows=1000 width=8) (actual time=10.212..10.214 rows=1 loops=1)
Output: (count(*))
Relations: Aggregate on (hits)
Remote SQL: SELECT count(*) FROM "default".hits WHERE (("URL" LIKE '%google%'))
FDW Time: 0.017 ms
Planning Time: 0.998 ms
Execution Time: 10.511 ms
Seems like pg_clickhouse is not properly recording the full time it spends planning and executing. Should that be its full time? Just planning?
- Dominant language
- C
- Stars
- 284
- Forks
- 21
- Avg merge
- 23h 1m
- Merged PRs (30d)
- 20
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ClickHouse/pg_clickhouse
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
ClickHouse/pg_clickhouse#383 · 1 comment ·
Maintainers usually reply within 1 day
-
data types enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
ClickHouse/pg_clickhouse#380 ·
Maintainers usually reply within 1 day
-
enhancement functions pushdown
Difficulty 3/5 1-2 days Newbie friendliness 68/100
ClickHouse/pg_clickhouse#379 ·
Maintainers usually reply within 1 day
-
Push down joins against an aggregated `IN (SELECT … GROUP BY … HAVING)` subquery (TPC-H Q18 shape)Possibly taken @JoshDreamland claimed this 2 days ago. Openenhancement pushdown sql
ClickHouse/pg_clickhouse#378 · 1 assignee ·
Maintainers usually reply within 1 day
-
operators pushdown
Difficulty 3/5 1-2 days Newbie friendliness 65/100
ClickHouse/pg_clickhouse#375 ·
Maintainers usually reply within 1 day
All issues in ClickHouse/pg_clickhouse
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ARM-software/sysarch-acs#556 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
netdata/netdata#24062 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100