Ecosyste.ms: Timeline
Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.
JelteF created a comment on a pull request on duckdb/pg_duckdb
Seems this improves perf by ~10% on most TPCDS queries when using `duckdb.force_execution = true`
Y-- opened a pull request on duckdb/pg_duckdb
Various improvements
* constify parameters in `pgduckdb_filter.cpp` * return early during conjonction evaluation * add variables in `InsertTupleIntoChunk` for clarity
Y-- created a branch on duckdb/pg_duckdb
yl/various-cleanup - DuckDB-powered Postgres for high performance apps & analytics.
JelteF pushed 1 commit to main duckdb/pg_duckdb
- Map DuckDB main schema to public (#329) After having some people play with the MotherDuck support we realized we sh... c770a46
JelteF closed a pull request on duckdb/pg_duckdb
Map DuckDB main schema to public
After having some people play with the MotherDuck support we realized we should be mapping the `main` schema to `public` to make it easy to access the tables that are in there.
JelteF created a review comment on a pull request on duckdb/pg_duckdb
Hmm, it seems I had a too new `clang-format` that did a bit more. Downgraded now for consistency to the version that is in our `dev_requirements.txt`. It doesn't seem to be formatted back with this...
Y-- created a review comment on a pull request on duckdb/pg_duckdb
Was this change triggered by `make format`? It feels like it goes the other way on my end :-) Maybe I'm not up to date?
Y-- created a review on a pull request on duckdb/pg_duckdb
Code LGTM. From an UX perspective I wonder if we won't want a flag to turn it off as it might be confusing for some power users. Though we can totally add later.
Y-- created a review on a pull request on duckdb/pg_duckdb
Code LGTM. From an UX perspective I wonder if we won't want a flag to turn it off as it might be confusing for some power users. Though we can totally add later.
Y-- closed a pull request on duckdb/pg_duckdb
Simplify `InsertTupleIntoChunk`
Now that we don't need to `duckdb_free`
JelteF pushed 5 commits to motherduck-map-main-to-public duckdb/pg_duckdb
- Invalidate buffer after release (#326) dbc0bd8
- Allocate buffer once per local state (#324) 511c618
- Revert "Allocate buffer once per local state (#324)" (#327) 8620dc8
- Allocate buffer once per local state (#328) dbeebf3
- Map DuckDB main schema to public After having some people play with the MotherDuck support we realized we should be ... f2312bc
JelteF created a comment on an issue on duckdb/pg_duckdb
Just for reference, there was another bug because `m_read_columns_ids` and `m_output_columns_ids` ideas are easy to confuse: [`ba2f7b3` (#328)](https://github.com/duckdb/pg_duckdb/pull/328/commits/...
Y-- opened a pull request on duckdb/pg_duckdb
Simplify `InsertTupleIntoChunk`
Now that we don't need to `pfree`
Y-- pushed 2 commits to yl/simplify-insert-tuple duckdb/pg_duckdb
Y-- closed a pull request on duckdb/pg_duckdb
Allocate buffer once per local state
As discussed in https://github.com/duckdb/pg_duckdb/issues/323: only allocate values and nulls buffers once per local state (i.e 1/ thread participating to the query) rather than once per call (tuple)
Y-- created a branch on duckdb/pg_duckdb
yl/simplify-insert-tuple - DuckDB-powered Postgres for high performance apps & analytics.
Y-- pushed 3 commits to yl/allocate-buffer-once-2 duckdb/pg_duckdb
JelteF created a branch on duckdb/pg_duckdb
motherduck-map-main-to-public - DuckDB-powered Postgres for high performance apps & analytics.
Y-- opened a pull request on duckdb/pg_duckdb
Allocate buffer once per local state
As discussed in https://github.com/duckdb/pg_duckdb/issues/323: only allocate values and nulls buffers once per local state (i.e 1/ thread participating to the query) rather than once per call (tuple)
Y-- created a branch on duckdb/pg_duckdb
yl/allocate-buffer-once-2 - DuckDB-powered Postgres for high performance apps & analytics.
Y-- pushed 1 commit to main duckdb/pg_duckdb
- Revert "Allocate buffer once per local state (#324)" (#327) 8620dc8