Re: Non-text mode for pg_dumpall - Mailing list pgsql-hackers

From tushar
Subject Re: Non-text mode for pg_dumpall
Date
Msg-id CAC6VRoa+7CxZ6kTYuxKH9A8H_MKkNEvjSaYv3QyiqJ=TpT0sfg@mail.gmail.com
Whole thread Raw
In response to Re: Non-text mode for pg_dumpall  (Mahendra Singh Thalor <mahi6run@gmail.com>)
List pgsql-hackers


On Fri, Dec 12, 2025 at 9:47 PM Mahendra Singh Thalor <mahi6run@gmail.com> wrote:

> [edb@1a1c15437e7c bin]$ ./psql postgres
> psql (19devel)
> Type "help" for help.
> postgres=# \dt
> Did not find any tables.
> postgres=#
>
> regards,
>

Hi Tushar,
This is the handling of command line arguments.
In code, after "-f", we expect file name, but here you are using "-C"
which will be considered as file name. This is the case for all the
command line arguments.

If pg_restore has the "-f" option, then the "-d database" name can't
be given and data will be copied into "-f filename" (it will not be
restored in the cluster).

Please let me know if you still have some doubts.

Thanks Mahendra , that was very helpful. 

Please refer this scenario where i am getting error like:
"psql:output_script4.sql:95: error: backslash commands are restricted; only \unrestrict is allowed" 
if i run the .sql file  generated by pg_restore command 

Steps to reproduce:
./pg_dumpall  -Ft -f  dump.tar
./pg_restore -Ft dump.tar  -C -v -f output_script.sql
run this .sql file against a new cluster ( \i output.script.sql)
restore will be done successfully but there are a few error like this 
psql:output_script4.sql:95: error: backslash commands are restricted; only \unrestrict is allowed

Is this expected? 

regards,

pgsql-hackers by date:

Previous
From: Babak Ghadiri
Date:
Subject: Parallelizing startup with many databases
Next
From: jian he
Date:
Subject: Re: Non-text mode for pg_dumpall