Could I ask you how many rows are in the flights_2008_7m table?
We have set hard limits on projections, because the operation it’s expensive, but on just 7 Millions records also if you trying to project all the columns of the table, you should be able to run the query regardless of the memory you have in the machine
as an example, I run this query on my notebook that has 32GB of memory without particular issues (well the query takes a long time to run because of the projection using lots ofcolumns)
omnisql> select * from flights_2008_7m;
7009728 rows returned.
Execution time: 21092 ms, Total time: 119800 ms
the space used by each row depends on the data type of each column.
to get the space taken by each column on the disk you can try this
omnisql> select count(*) from flights_2008_7m;
1 rows returned.
Execution time: 18 ms, Total time: 20 ms
omnisql> show table details flights_2008_7m ;
then take the total_data_file_size and divide for the number of rows you got with count(*)
so in this case, 1610612736/7009728 so around 229 bytes per row.
Anyway, when you run a query the 229 number could be different and it’s likely that you need more memory.
Please check the number of rows you got in the table because the very big number looks to be a bug.