Jelte Fennema-Nio
Jelte Fennema-Nio
> when I merge with main I can't resolve a crash in test/regression/sql/query_filter.sql SELECT a, c FROM query_filter_output_column WHERE b = 't1'; is what triggers it, it's a EXC_BAD_ACCESS somewhere...
> I'd like to stop having to fix this with every PR that gets merged Totally makes sense. Let's merge this quickly now.
Based on some research I did this should be quite easy to address, postgres_scanner is able to do this. I'm pretty sure it's a few lines of code only. So...
If it's indeed resolved we should add some tests to make sure we don't regress again.
@CaselIT can you try that new again with the current main branch? #531 might very well change the behavior you're describing.
Alright, can you create a separate issue for this?
Is there still something actionable here for the 0.1.0 release?
Closing this in favor of #243 (I didn't realise this issue was still open when I created that one). This issue was resolved, but we'll now revert its implementation for...
I'm going to move this issue to 0.2.0, so we can start stability testing for 0.1.0. This is an important issue, but we fixed the worst cases. We'll fix more...
To make the build faster it would help a lot if you changed the `make install` commands to be parallel, by using e.g. `make -j10 install`. Or maybe `make -j$(nproc)...