Since the query is pretty wide (contains multiple joins) the execution plan will try to make all joins and only then try to filter unnecessary rows. This causes PG to load a huge temporary table into memory, and since it's too big to fit in, the CPU sky rockets.