php artisan migrate tries to create migrations table again

[dennis-koster]

• Laravel Version: v9.42.2
• PHP Version: 8.1.11
• Database Driver & Version: PostgreSQL 13 (Digital Ocean)

Description:

After upgrading my php version from 8.0 to 8.1, and Laravel from v8.83.6 to v9.42.2, my migrations are no longer working. It appears that the migrate command, as well as the migrate:status command struggle to find the existing migrations table. It therefor tries to create it, but it actually already exists.

Querying the migrations table in tinker reveals that there are records in there. Also, the fact that the migrate command returns a Duplicate table SQL error seems to prove that it can in fact connect to the database.

php artisan tinker;
DB::table('migrations')->count(); // 206

Steps To Reproduce:

php artisan migrate:status
ERROR  Migration table not found.

php artisan migrate
INFO  Preparing database.  

Creating migration table ................................................................................................................ 8ms FAIL

In Connection.php line 760:
                                                                                                                                                                                                                 
SQLSTATE[42P07]: Duplicate table: 7 ERROR:  relation "migrations" already exists (SQL: create table "migrations" ("id" serial primary key not null, "migration" varchar(255) not null, "batch" integer not null))  
                                                                                                                                                                                                                 

In Connection.php line 545:
                                                                                
SQLSTATE[42P07]: Duplicate table: 7 ERROR:  relation "migrations" already exists  

[adamjgriffith]

Possibly related to: https://laravel.com/docs/9.x/upgrade#postgres-schema-configuration

[dennis-koster]

Thanks for the suggestion. I had neglected to change this configuration value. However, unfortunately, this did not solve the issue.

[untungso]

I'm having this similar issue, not sure what happened

[nikosv]

The same happened to me, any solutions so far?

[unlike777]

I had such a case

If you have pgbouncer and routing is configured via the DB name db_master/db_slave, then in Laravel 9 and 10 you will catch the same error.

This is because the condition \vendor\laravel\framework\src\Illuminate\Database\Schema\Grammars\PostgresGrammar.php lines 76 and 86

table_catalog = ?

When building or deploying the application, you need to patch this file and remove this condition.

This was fixed in Laravel 11, cuz they completely changed query there

[hafezdivandari]

May have been fixed on Laravel 10.34+ via #49020 ?

[unlike777]

nope

[hafezdivandari]

For PostgreSQL, this has been fixed on Laravel 11.x via #49148 to avoid breaking change.

[unlike777]

yes, which is what I wrote above))

This was fixed in Laravel 11, cuz they completely changed query there