Supabase db dump cannot find -f

[garthoid]

I am following the documentation at: https://supabase.com/docs/guides/platform/migrating-within-supabase/backup-restore

I am attempting to Backup database using the CLI and using the Session pooler connection string.

supabase db dump --db-url postgresql://postgres.brerhjusaiijlnkmdlgw:[password]@aws-0-ca-central-1.pooler.supabase.com:5432/postgres -f ./roles.sql --role-only

This proceeds to dump the sql to standard out. At the end I see:

-f: command not found.

Baffled, I check:
`supabase db dump -h
Dumps data or schemas from the remote database

Usage:
supabase db dump [flags]

Flags:
--data-only Dumps only data records.
--db-url string Dumps from the database specified by the connection string (must be percent-encoded).
--dry-run Prints the pg_dump script that would be executed.
-x, --exclude strings List of schema.tables to exclude from data-only dump.
-f, --file string File path to save the dumped contents.
-h, --help help for dump
--keep-comments Keeps commented lines from pg_dump output.
--linked Dumps from the linked project. (default true)
--local Dumps from the local database.
-p, --password string Password to your remote Postgres database.
--role-only Dumps only cluster roles.
-s, --schema strings Comma separated list of schema to include.
--use-copy Uses copy statements in place of inserts.

Global Flags:
--create-ticket create a support ticket for any CLI error
--debug output debug logs to stderr
--dns-resolver [ native | https ] lookup domain names using the specified resolver (default native)
--experimental enable experimental features
--network-id string use the specified docker network instead of a generated one
-o, --output [ env | pretty | json | toml | yaml ] output format of status variables (default pretty)
--workdir string path to a Supabase project directory
`

Sure enough, -f is there.

So I am baffled, what is wrong with my command? For reference:

supabase --version 2.20.3

Please advise.

[adamthewebguy]

Hey, I had the same thing this morning. It turned out it was how I'd pasted the command into my terminal.
It had done it like this:

supabase db dump --db-url postgresql://postgres.blah:my-db-pswd@aws-0-us-west-1.pooler.supabase.com:5432/postgres
-f roles.sql --role-only

It was running the first line (verified by emitting a log of stuff in the terminal!) but then looking to run the second line as a new command.

I ran it as a single line....

supabase db dump --db-url postgresql://postgres.blah:my-db-pswd@aws-0-us-west-1.pooler.supabase.com:5432/postgres -f roles.sql --role-only

And all good!