Native lakehouse experience in Postgres powered by DuckDB & DuckLake
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 77%
Response Time: 2d
First Timer Success: 50%
relytcloud/pg_ducklake has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in relytcloud/pg_ducklake respond to incoming external pull requests in approximately 57.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 56.6 places relytcloud/pg_ducklake in the A tier.
The external contributor pull request merge rate for relytcloud/pg_ducklake is 76.9%, based on public PR activity from non-core contributors.
relytcloud/pg_ducklake currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in relytcloud/pg_ducklake. Reviews community pull requests with focus on project quality.
Discussions in relytcloud/pg_ducklake focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/relytcloud/pg_ducklake?utm_source=github&utm_medium=badge)
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~38 hours (96% approval). Large PRs (>500 lines) take ~278 hours (35% approval). Keep your diff compact for rapid review.
Environment: pg_ducklake 1.1.0, PostgreSQL 18.6, Apache Hop "PostgreSQL Bulk Loader" (COPY ... FROM STDIN WITH CSV). Problem: COPY ... FROM STDIN into a USING ducklake table fails if any column is NOT NULL: ERROR: COPY FROM STDIN cannot use the native writer for this DuckLake table Detail: Constraints, generated or identity columns, triggers, rules, and row-level security are not supported by the native COPY producer. CREATE TABLE ... (col bigint NOT NULL) USING ducklake succeeds, and INSERT works, so the table is usable except for COPY. In CheckNativeCopySemantics() (copy_from.cpp) constr->has_not_null makes the table unsupported, and there is no fallback because the DuckDB path cannot consume the COPY stream.
Hi, is this a bug or am I doing something wrong? I am running analytical backfills. It succeeded for most partitions, but on almost all of the failed queries, it says "parquet not found" for whichever underlying parquet the query was using. And the timestamp collided with my postgresql's log of ducklake background worker merging adjacent parquet files. I am using BEGIN TRANSACTION though, so, is this a bug or I'm doing something wrong? Be happy to provide more details, thank you for your help.
Description Support creating materialized view using pg_ducklake for Postgres (row-store) heap tables. Speed up analytics to have a simple HTAP experience. Refresh matview should also be covered.
Description Support \dt+ and pg_relation_size for ducklake table.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to relytcloud/pg_ducklake, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of relytcloud/pg_ducklake acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 76.9% were successfully merged into the primary branch.
relytcloud/pg_ducklake has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 56.6 places relytcloud/pg_ducklake in the Welcoming tier.
The external pull request merge rate is 76.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, relytcloud/pg_ducklake currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for relytcloud/pg_ducklake are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.