What would be the workaround for the same error if we are using Redis as a cache, PostgreSQL in cluster mode, and a connection pool?

[mtt786]

I'm not sure there is a way around this on our end. This how Postgres works if a query error is encountered within a transaction, and the database cache works atomically by attempting to insert the record and if it gets an exception it will update the record instead. This is similar to the approach Symfony takes.

So, my work around suggestion is to define a separate connection in your Laravel configuration for the cache.

Then, set your lock_connection in your cache configuration file:

Originally posted by @taylorotwell in #36280