In general no, it is expected to happen. Basically what that error message means is that when Postgres was doing its automatic background table cleanup tasks, a query came in that couldn't run with the cleanup task concurrently, so Postgres canceled cleaning up to let the query run. Unfortunately Postgres logs it at an "error" level instead of an "info" or other less severe level.
Steve Busko
The server logs contain entries like the following:
is this a problem?