This can happen for some valid Postgres queries due to an issue with the
library handling large nested queries. As such it's safest to just
ignore any queries that fail to parse.