Redis, yes. Perfect for this kind of thing. delayed_job might make less sense, since delayed_job still INSERTs to the database.
I haven't benchmarked it specifically but I'd have to guess your time savings to store the information in a postgresql job queue vs the visits table would be negligible at best.
Could this send to redis or a delayed job and be eventually consistent to database for non-logged in users?