supabase db pull do not capture all content in remote schema when there is no migration history

[matteovava]

Affected area

Database

Supabase CLI version

2.109.1

Operating system

macOS Tahoe 26.5.1

Installation method

brew

Command

supabase db pull

Actual output

Initialising login role...
Creating shadow database...
Initialising schema...
Seeding globals from roles.sql...
Diffing schemas...
No schema changes found
Try rerunning the command with --debug to troubleshoot the error.

Expected behavior

When i run supabase db pull in a newly created environment without any entries in the migration table it should use pg_dump to capture all content of the remote schema, as described in the documentation.

Steps to reproduce

1. Create a new Supabase project
2. run supabase init in the local environment
3. link the remote project using supabase link
4. run supabase db pull and it will says "no schema changes found" even if there are no migration on the remote:

Initialising login role...
Creating shadow database...
Initialising schema...
Seeding globals from roles.sql...
Diffing schemas...
No schema changes found
Try rerunning the command with --debug to troubleshoot the error.

Crash report ID

No response

Docker and service versions

docker version
Client:
 Version:           29.6.1
 API version:       1.55
 Go version:        go1.26.4
 Git commit:        8900f1d
 Built:             Fri Jun 26 11:39:35 2026
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.80.0 (232116)
 Engine:
  Version:          29.6.1
  API version:      1.55 (minimum version 1.40)
  Go version:       go1.26.4
  Git commit:       8ec5ab3
  Built:            Fri Jun 26 11:39:58 2026
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          v2.2.5
  GitCommit:        e53c7c1516c3b2bff98eb76f1f4117477e6f4e66
 runc:
  Version:          1.3.6
  GitCommit:        v1.3.6-0-g491b69ba
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

SERVICE IMAGE          | LOCAL                  | LINKED     
  ------------------------|------------------------|------------
   supabase/postgres      | 17.6.1.141             | 17.6.1.141 
   supabase/gotrue        | v2.192.0               | v2.192.0   
   postgrest/postgrest    | v14.5                  | v14.5      
   supabase/realtime      | v2.112.6               | -          
   supabase/storage-api   | v1.61.10               | v1.61.10   
   supabase/edge-runtime  | v1.74.2                | -          
   supabase/studio        | 2026.07.06-sha-66cf431 | -          
   supabase/postgres-meta | v0.96.6                | -          
   supabase/logflare      | 1.46.0                 | -          
   supabase/supavisor     | 2.9.7                  | -

Additional context

No response

[hiSandog]

The empty-history path should treat the local baseline as an empty schema and compare it with the linked remote database, not infer that there is nothing to pull from the migration table. A regression fixture should cover a missing migrations table and an existing-but-empty one, with remote tables, functions, extensions, and grants, then assert the generated initial migration can recreate that schema. The debug output should also print which schemas were included/excluded so a genuine empty diff can be distinguished from connecting to or filtering the wrong database.

[Korat-Dishant]

according to this guid https://supabase.com/blog/supabase-local-dev and this https://youtu.be/N0Wb85m3YMI. running Supabase db remote commit should save the problem. but while running the command it says Command "commit" is deprecated, use "db pull" instead.

Command "commit" is deprecated, use "db pull" instead.

Initialising login role...
Connecting to remote database...
Creating shadow database...
Initialising schema...
Seeding globals from roles.sql...
Diffing schemas...
No schema changes found
Try rerunning the command with --debug to troubleshoot the error.

and db pull is not useful in this case either.

[Korat-Dishant]

It seems that the problem is with experimental schema diff engine. if you turn off the flag and fall back to legacy migration engine, it seems to solve the problem.

# pg-delta is the schema diff engine for db diff / db pull / db remote commit.
# Set enabled = false to fall back to the legacy migra engine.
[experimental.pgdelta]
enabled = false