failed_jobs driver not found

I've set-up a new Laravel (10.44.0) environment and all is working. But, when running a job and it fails, I'm getting the bellow error.

could not find driver (Connection: postgres, SQL: insert into "failed_jobs" ("uuid", "connection", "queue", "payload", "exception", "failed_at") values (9b66c3d1-0cba-473b-8443-77840cae4c78, redis, default, {"data":{"command":"O:36:\"Illuminate\Events\CallQueuedListener\":19:{s:5:\"class\";s:35:\"App\Listeners\UpsertAudienceProfile\";s:6:\"method\";s:6:\"handle\";s:4:\"data\";a:1:{i:0;O:32:\"App\Events\AudienceProfileUpdate\":2:{s:4:\"data\";a:2:{s:4:\"name\";s:8:\"John Doe\";s:3:\"age\";s:2:\"19\";}s:8:\"personId\";N;}}s:5:\"tries\";N;s:13:\"maxExceptions\";N;s:7:\"backoff\";N;s:10:\"retryUntil\";N;s:7:\"timeout\";N;s:17:\"shouldBeEncrypted\";b:0;s:3:\"job\";N;s:10:\"connection\";N;s:5:\"queue\";N;s:15:\"chainConnection\";N;s:10:\"chainQueue\";N;s:19:\"chainCatchCallbacks\";N;s:5:\"delay\";N;s:11:\"afterCommit\";N;s:10:\"middleware\";a:0:{}s:7:\"chained\";a:0:{}}","commandName":"Illuminate\Events\CallQueuedListener"},"maxTries":null,"failOnTimeout":false,"attempts":1,"type":"event","timeout":null,"tags":{},"id":"9b66c3d1-0cba-473b-8443-77840cae4c78","maxExceptions":null,"pushedAt":"1709868690.9921","job":"Illuminate\Queue\CallQueuedHandler@call","uuid":"9b66c3d1-0cba-473b-8443-77840cae4c78","silenced":false,"retryUntil":null,"backoff":null,"telescope_uuid":"9b82fb98-0aa5-446a-9488-fa5723ecbf3b","displayName":"App\Listeners\UpsertAudienceProfile"}, Illuminate\Queue\MaxAttemptsExceededException: App\Listeners\UpsertAudienceProfile has been attempted too many times. in /var/www/audience-platform-web-app/vendor/laravel/framework/src/Illuminate/Queue/MaxAttemptsExceededException.php:24

Some additional info:

• I'm using Postgres 16.2;
• Installed and enabled pgsql and pdo_pgsql, but didn't help;
• Tried to use sqlite, but there seems to be another issue, because when setting up different DB for failed jobs, it is not used;

• It seems like when using MySQL/MariaDB this issue is not there, so something with Postgres...!?;

All help is much appreciated. Thanks in advance!