I also was getting that error that was nearly crashing my server. The issue is the database command yarn database:setup, what I had to do to fix this was clear my postgresDB and run the command yarn database:migrate instead. Seems the issue is the default data that gets inserted using the setup version of the command.
In reality I wouldn't think this error should cause CPU overload, maybe the authors of the project could lower the amount of logs written?