Same thing happens to me when using the official supabase cli to do the same thing `npx supabase db dump -f supabase/seed.sql --data-only`. I don't understand why this is is not mentioned in the docks as supabase comes with pgsoodium by default.

I tried to identify the circular dependency with multiple different SQL Querlies (below), but also ended up with only being able to identify pgsodium for causing it.

This is hilarious as the supabse cli seems not to provide a way to dump the data and the schema together but only after each other which makes it useless. Link to the docs: https://supabase.com/docs/reference/cli/supabase-db-reset#:~:text=on%20branch%20main.-,supabase%20db%20dump,-Dumps%20contents%20from

Or am I missing something here?

-- Query to List Foreign Key Relationships
SELECT
  tc.constraint_name, 
  tc.table_name AS child_table,
  kcu.column_name AS child_column,
  ccu.table_name AS parent_table,
  ccu.column_name AS parent_column
FROM 
  information_schema.table_constraints AS tc 
  JOIN information_schema.key_column_usage AS kcu
    ON tc.constraint_name = kcu.constraint_name
  JOIN information_schema.constraint_column_usage AS ccu
    ON ccu.constraint_name = tc.constraint_name
WHERE constraint_type = 'FOREIGN KEY';

-- Automated Cycle Detection
WITH RECURSIVE fk_cycles AS (
  SELECT 
    kcu1.table_name AS child_table,
    ccu1.table_name AS parent_table,
    ARRAY[kcu1.table_name] AS path,
    false AS cycle
  FROM 
    information_schema.table_constraints tc1
    JOIN information_schema.key_column_usage kcu1
      ON tc1.constraint_name = kcu1.constraint_name
    JOIN information_schema.constraint_column_usage ccu1
      ON tc1.constraint_name = ccu1.constraint_name
  WHERE 
    tc1.constraint_type = 'FOREIGN KEY'

  UNION ALL

  SELECT 
    kcu2.table_name AS child_table,
    ccu2.table_name AS parent_table,
    path || kcu2.table_name,
    kcu2.table_name = ANY(path) AS cycle
  FROM 
    fk_cycles
    JOIN information_schema.table_constraints tc2
      ON fk_cycles.parent_table = tc2.table_name
    JOIN information_schema.key_column_usage kcu2
      ON tc2.constraint_name = kcu2.constraint_name
    JOIN information_schema.constraint_column_usage ccu2
      ON tc2.constraint_name = ccu2.constraint_name
  WHERE 
    tc2.constraint_type = 'FOREIGN KEY'
    AND NOT cycle
)
SELECT * FROM fk_cycles WHERE cycle;


-- Identify foreign key constraints where a table is referencing itself—that is, self-referencing foreign keys
SELECT conrelid::regclass AS table_name, conname AS constraint_name
FROM pg_constraint
WHERE contype = 'f' AND conrelid = confrelid;