There are a number of innovations that make Didgets extremely fast and parallelizing queries is certainly one of them.
When I performed the benchmarks against Postgres, I assumed that parallelization was on by default. I certainly saw output when I performed the EXPLAIN ANALYZE operations that indicated it was working (e.g. 'Workers Planned', 'Workers Launched' and 'Parallel Bitmap Heap Scan...'). I haven't worked extensively with Postgres since version 9.5 so I haven't kept up on all the configuration settings.
After getting this message, I went into the Postgresql.conf file and bumped up the values for max_worker_processes and max_parallel_workers. This seemed to make some of the queries a bit faster, but I have not re-run the benchmarks in the video.